Methods of managing communication based on information defining an operational environment and related nodes

ABSTRACT

Methods may be provided to operate a Radio Access Network RAN node of a wireless communication network. Information defining an operational environment in which a wireless device is operating may be obtained. Communication with the wireless device may be managed based on the information defining the operational environment in which the wireless device is operating. Related RAN nodes, computer programs, and computer program products are also discussed.

TECHNICAL FIELD

The present disclosure relates generally to communications, and moreparticularly to communication methods and related devices and nodessupporting wireless communications.

BACKGROUND

To support increased traffic capacity and to enable the transmissionbandwidth to support high data rate services, 5G will extend the rangeof frequencies used for mobile communication. This includes new spectrumbelow 6 GHz, as well as spectrum in higher frequency bands such as 28GHz. High frequency bands may provide contiguous larger bandwidth forhigher rates in data communication. In such high frequency bands, theradio links may be susceptible to rapid channel variations and maysuffer from severe pathloss and atmospheric absorption. To address thesechallenges, the base stations and the mobile terminals in 5G will usehighly directional antennas for beamforming to achieve sufficient linkbudget in a wide area network.

Depending upon the possibility of generating and projecting a number ofbeams, three different beamforming techniques can be used. Thesetechniques include analog beamforming, hybrid beam forming, and digitalbeamforming, and these techniques are discussed below.

The analog beamforming approach shapes the beam through a signal RadioFrequency (RF) chain for all the antenna elements. The processing isdone in the analog domain and it may only be possible totransmit/receive a beam in one direction at a time.

The hybrid beamforming approach may require RF chains equivalent to thenumber of beams to be formed. An N RF chain hybrid beamformer may thusproduce N beams and may enable the transceiver to transmit/receive Nanalog beams in N simultaneous directions.

The digital beamforming (unlike hybrid and analog beamformingarchitectures) approach may require a separate RF chain and dataconverters for each antenna element and may allow processing of thereceived signals in the digital domain. Digital beamforming maypotentially allow a transceiver to direct beams in infinite directions.

As the radio link signal is beamformed, the precision in the transmitterand the receiver beam alignment may have important implications withrespect to initial access, handover and beam tracking procedures.Efficient beam management therefore has been a hot issue forimproved/optimized 5G network operation and contains three-foldoperations, including beam establishment, beam adjustment, and beamrecovery. In the following discussion, brief elaboration of the threebeam management operations is provided.

The beam establishment procedure includes operations of beam sweeping,beam measurements, beam determination, and beam reporting as discussedbelow.

A beam sweeping procedure is illustrated in FIG. 1 . During beamsweeping, a geographical area is covered by a set of beams transmittedand received according to pre-defined intervals in time and direction inthe Downlink (DL). As shown in FIG. 1 , SS Block 1 (including 4 blocks)may be transmitted using a first beam in a first direction, SS Block 2(including 4 blocks) may be transmitted using a second beam in a seconddirection (after the first beam), SS Block 3 (including 4 blocks) may betransmitted using a third beam in a third direction (after the secondbeam), SS Block 4 (including 4 blocks) may be transmitted using a fourthbeam in a fourth direction (after the third beam), and SS Block 5(including 4 blocks) may be transmitted using a fifth beam in a fifthdirection (after the fourth beam).

The beam measurement procedure may be valid for both uplink UL anddownlink DL transmission. During the beam measurement procedure, thequality of the received signal at the gNodeB (for UL) or at the UE (forDL) is evaluated. In DL, the User Equipment (UE) measures the beams fromthe gNodeB and analyses them based on received signal strength in eachbeam. A similar procedure is carried out at the gNodeB where the beamcoming from the UE is measured for each beam.

During the beam determination procedure, a suitable beam is determinedin the gNodeB and UE based on the beam measurements performed in theDownlink (DL) and in the Uplink (UL).

The beam reporting procedure is used by the UE to report the beamquality and the beam decision information to the radio access network.

A beam reporting procedure is illustrated in FIG. 2A. Beam adjustment isdiscussed below with respect to FIGS. 2B (illustrating DownLink DLtransmitter-side beam adjustment) and 2C (illustrating DL receiver-sidebeam adjustment). Once an initial beam pair has been established, theremay be a need to regularly re-evaluate the selection of transmitter-sideand receiver-side beam directions due to movement and/or rotation of themobile device. The beam adjustment procedure may also include refiningthe beam shapes and includes re-evaluation of both transmitter side andreceiver side beam adjustment. Conventionally UL/DL beam correspondenceis considered so that beam adjustment done in either direction oftransmission is also considered valid for the other direction oftransmission. FIG. 2B illustrates Downlink DL transmitter-side (RANnode, also referred to as a base station, gNB, gNodeB, etc.) beamadjustment, and FIG. 2C illustrates DL receiver-side (UE) beamadjustment.

Beam Recovery is discussed below.

When a UE in connected mode experiences a poor channel condition, itreceives a beam failure recovery indication from the lower layerentities. The UE then transmits a request for beam recovery to thegNodeB.

The beam management procedure may typically be handled via NR-Uu andLTE-Uu interfaces as shown in FIG. 3 . Exploitation of the normativeprotocol may depend on the NR standalone or non-standalone deploymentstrategies. Beam management is illustrated in FIG. 3 with respect toNG-RAN Rel-15 LCS Protocols.

Current beam management procedures may less effective in some situationsin non-line of sight communications, for example, if the UE is indoorsand/or subject to a reflected signal path.

SUMMARY

According to some embodiments of inventive concepts, methods may beprovided to operate a Radio Access Network RAN node of a wirelesscommunication network. Information defining an operational environmentin which a wireless device is operating may be obtained. Communicationwith the wireless device may be managed based on the informationdefining the operational environment in which the wireless device isoperating.

By providing information defining the operational environment, the RANnode may be able to provide improved beam management, improved handoveroperations, and/or improved carrier aggregation.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a furtherunderstanding of the disclosure and are incorporated in and constitute apart of this application, illustrate certain non-limiting embodiments ofinventive concepts. In the drawings:

FIG. 1 is a diagram illustrating beam sweeping procedures;

FIG. 2A is a diagram illustrating beam reporting/adjustment procedures;

FIG. 2B is a diagram illustrating downlink transmitter-side beamadjustment;

FIG. 2C is a diagram illustrating downlink receiver-side beamadjustment;

FIG. 3 is a block diagram illustrating NG-RAN Release 15 LCS protocols;

FIG. 4 is a flow chart illustrating UE operations according to someembodiments;

FIG. 5 is a flow chart illustrating base station operations according tosome embodiments;

FIG. 6 is a flow chart illustrating a location server operationaccording to some embodiments;

FIG. 7 is a table an information element used to communicate a locationinformation source according to some embodiments;

FIG. 8A is a diagram illustrating a UE location/environment resulting inmultiple paths of communication between a network node and a UEaccording to some embodiments;

FIG. 8B is a diagram illustrating a power delay profile corresponding tothe multiple paths of FIG. 8A according to some embodiments;

FIG. 9 is a diagram illustrating a power delay provide corresponding toline-of-sight LOS communication according to some embodiments;

FIG. 10A illustrates a table providing beam association informationaccording to some embodiments;

FIG. 10B illustrates a table that may be used by a base station toidentify beam adjustment configurations/parameters according to someembodiments;

FIG. 11 is a block diagram illustrating a wireless communication deviceUE according to some embodiments of inventive concepts;

FIG. 12 is a block diagram illustrating a radio access network RAN node(e.g., a base station eNB/gNB) according to some embodiments ofinventive concepts;

FIG. 13 is a block diagram illustrating a core network CN node (e.g., anAMF node, an SMF node, etc.) according to some embodiments of inventiveconcepts;

FIGS. 14, 15, 16A, 16B, 17, 18A, 18B, 19A, 19B, and 20 are flow chartsillustrating operations of a RAN node according to some embodiments ofinventive concepts;

FIG. 21 is a block diagram of a wireless network in accordance with someembodiments,

FIG. 22 is a block diagram of a user equipment in accordance with someembodiments;

FIG. 23 is a block diagram of a virtualization environment in accordancewith some embodiments;

FIG. 24 is a block diagram of a telecommunication network connected viaan intermediate network to a host computer in accordance with someembodiments:

FIG. 25 is a block diagram of a host computer communicating via a basestation with a user equipment over a partially wireless connection inaccordance with some embodiments;

FIG. 26 is a block diagram of methods implemented in a communicationsystem including a host computer, a base station and a user equipment inaccordance with some embodiments;

FIG. 27 is a block diagram of methods implemented in a communicationsystem including a host computer, a base station and a user equipment inaccordance with some embodiments;

FIG. 28 is a block diagram of methods implemented in a communicationsystem including a host computer, a base station and a user equipment inaccordance with some embodiments; and

FIG. 29 is a block diagram of methods implemented in a communicationsystem including a host computer, a base station and a user equipment inaccordance with some embodiments.

DETAILED DESCRIPTION

Inventive concepts will now be described more fully hereinafter withreference to the accompanying drawings, in which examples of embodimentsof inventive concepts are shown. Inventive concepts may, however, beembodied in many different forms and should not be construed as limitedto the embodiments set forth herein. Rather, these embodiments areprovided so that this disclosure will be thorough and complete, and willfully convey the scope of present inventive concepts to those skilled inthe art. It should also be noted that these embodiments are not mutuallyexclusive. Components from one embodiment may be tacitly assumed to bepresent/used in another embodiment.

The following description presents various embodiments of the disclosedsubject matter. These embodiments are presented as teaching examples andare not to be construed as limiting the scope of the disclosed subjectmatter. For example, certain details of the described embodiments may bemodified, omitted, or expanded upon without departing from the scope ofthe described subject matter.

FIG. 11 is a block diagram illustrating elements of a wirelesscommunication device UE 300 (also referred to as a mobile terminal, amobile communication terminal, a wireless device, a wireless terminal,mobile device, a wireless communication terminal, user equipment, UE, auser equipment node/terminal/device, etc.) configured to providewireless communication according to embodiments of inventive concepts.(Wireless device 300 may be provided, for example, as discussed belowwith respect to wireless device 4110 of FIG. 21 .) As shown, wirelessdevice UE may include an antenna 307 (e.g., corresponding to antenna4111 of FIG. 21 ), and transceiver circuitry 301 (also referred to as atransceiver, e.g., corresponding to interface 4114 of FIG. 21 )including a transmitter and a receiver configured to provide uplink anddownlink radio communications with a base station(s) (e.g.,corresponding to network node 4160 of FIG. 21 , also referred to as aRAN node) of a radio access network. Wireless device UE may also includeprocessing circuitry 303 (also referred to as a processor, e.g.,corresponding to processing circuitry 4120 of FIG. 21 ) coupled to thetransceiver circuitry, and memory circuitry 305 (also referred to asmemory, e.g., corresponding to device readable medium 4130 of FIG. 21 )coupled to the processing circuitry. The memory circuitry 305 mayinclude computer readable program code that when executed by theprocessing circuitry 303 causes the processing circuitry to performoperations according to embodiments disclosed herein. According to otherembodiments, processing circuitry 303 may be defined to include memoryso that separate memory circuitry is not required. Wireless device UEmay also include an interface (such as a user interface) coupled withprocessing circuitry 303, and/or wireless device UE may be incorporatedin a vehicle.

As discussed herein, operations of wireless device UE may be performedby processing circuitry 303 and/or transceiver circuitry 301. Forexample, processing circuitry 303 may control transceiver circuitry 301to transmit communications through transceiver circuitry 301 over aradio interface to a radio access network node (also referred to as abase station) and/or to receive communications through transceivercircuitry 301 from a RAN node over a radio interface. Moreover, modulesmay be stored in memory circuitry 305, and these modules may provideinstructions so that when instructions of a module are executed byprocessing circuitry 303, processing circuitry 303 performs respectiveoperations (e.g., operations discussed below with respect to ExampleEmbodiments relating to wireless devices).

FIG. 12 is a block diagram illustrating elements of a radio accessnetwork RAN node 400 (also referred to as a network node, base station,eNodeB/eNB, gNodeB/gNB, etc.) of a Radio Access Network (RAN) configuredto provide cellular communication according to embodiments of inventiveconcepts. (RAN node 400 may be provided, for example, as discussed belowwith respect to network node 4160 of FIG. 21 .) As shown, the RAN nodemay include transceiver circuitry 401 (also referred to as atransceiver, e.g., corresponding to portions of interface 4190 of FIG.21 ) including a transmitter and a receiver configured to provide uplinkand downlink radio communications with mobile terminals. The RAN nodemay include network interface circuitry 407 (also referred to as anetwork interface, e.g., corresponding to portions of interface 4190 ofFIG. 21 ) configured to provide communications with other nodes (e.g.,with other base stations) of the RAN and/or core network CN. The networknode may also include processing circuitry 403 (also referred to as aprocessor, e.g., corresponding to processing circuitry 4170) coupled tothe transceiver circuitry, and memory circuitry 405 (also referred to asmemory, e.g., corresponding to device readable medium 4180 of FIG. 21 )coupled to the processing circuitry. The memory circuitry 405 mayinclude computer readable program code that when executed by theprocessing circuitry 403 causes the processing circuitry to performoperations according to embodiments disclosed herein. According to otherembodiments, processing circuitry 403 may be defined to include memoryso that a separate memory circuitry is not required.

As discussed herein, operations of the RAN node may be performed byprocessing circuitry 403, network interface 407, and/or transceiver 401.For example, processing circuitry 403 may control transceiver 401 totransmit downlink communications through transceiver 401 over a radiointerface to one or more mobile terminals UEs and/or to receive uplinkcommunications through transceiver 401 from one or more mobile terminalsUEs over a radio interface. Similarly, processing circuitry 403 maycontrol network interface 407 to transmit communications through networkinterface 407 to one or more other network nodes and/or to receivecommunications through network interface from one or more other networknodes. Moreover, modules may be stored in memory 405, and these modulesmay provide instructions so that when instructions of a module areexecuted by processing circuitry 403, processing circuitry 403 performsrespective operations (e.g., operations discussed below with respect toExample Embodiments relating to RAN nodes).

According to some other embodiments, a network node may be implementedas a core network CN node without a transceiver. In such embodiments,transmission to a wireless device UE may be initiated by the networknode so that transmission to the wireless device is provided through anetwork node including a transceiver (e.g., through a base station orRAN node). According to embodiments where the network node is a RAN nodeincluding a transceiver, initiating transmission may includetransmitting through the transceiver.

FIG. 13 is a block diagram illustrating elements of a core network CNnode (e.g., an SMF node, an AMF node, etc.) of a communication networkconfigured to provide cellular communication according to embodiments ofinventive concepts. As shown, the CN node may include network interfacecircuitry 507 (also referred to as a network interface) configured toprovide communications with other nodes of the core network and/or theradio access network RAN. The CN node may also include a processingcircuitry 503 (also referred to as a processor) coupled to the networkinterface circuitry, and memory circuitry 505 (also referred to asmemory) coupled to the processing circuitry. The memory circuitry 505may include computer readable program code that when executed by theprocessing circuitry 503 causes the processing circuitry to performoperations according to embodiments disclosed herein. According to otherembodiments, processing circuitry 503 may be defined to include memoryso that a separate memory circuitry is not required.

As discussed herein, operations of the CN node may be performed byprocessing circuitry 503 and/or network interface circuitry 507. Forexample, processing circuitry 503 may control network interfacecircuitry 507 to transmit communications through network interfacecircuitry 507 to one or more other network nodes and/or to receivecommunications through network interface circuitry from one or moreother network nodes. Moreover, modules may be stored in memory 505, andthese modules may provide instructions so that when instructions of amodule are executed by processing circuitry 503, processing circuitry503 performs respective operations (e.g., operations discussed belowwith respect to Example Embodiments relating to core network nodes).

Beam management procedures and/or RRM procedures (such asmobility/handover) may currently rely on Reference Signal Received Power(RSRP) measurements on beams that convey a reference signal or a set ofreference signals for beam measurement. As an enhancement, reference [1](U.S. Pat. No. 6,512,481) uses the location of the UE as an input fromthe UE for beam adjustment. To adjust a beam, UE geo-location data basedon Global Positioning (GPS) measurement may be used to compute an angleof arrival/departure and range of the radio signal. By using thedetermined angle of arrival/departure and range, the beamformer may thendeterministically modify the radio signal beam projection from the BaseStation (BS) to the UE and vice-versa. However, in a situation when a UEis indoors (or otherwise out of GPS coverage) the deterministic beamadjustment may not work. In addition, when the UE changes its locationafter reporting its geo-location data, the aforementioned beamadjustment protocol may be less effective. Therefore, in order toidentify an improved/optimal beam projection for efficient beammanagement and/or to improve handovers, it may also be useful toincorporate side information of the environment and/or condition whichthe UE is experiencing at the time of beam.

According to some embodiments of the present disclosure, mechanisms maybe provided to improve beam adjustment that can be useful for variousRAN procedures.

Including the beam measurement (RSRP of a reference signal transmittedin beam for measurement), some embodiments of inventive concepts mayalso use on additional information reported by the UE to provide moreefficient beam adjustment. Some embodiments of inventive concepts may beincorporated in both NR stand alone and NR non-standalone deploymentstrategies.

FIG. 4 is a flow chart illustrating UE operations according to someembodiments of inventive concepts. At operation 100, the UE may receivethe best beam in DL based upon the reported beam measurement. Atoperation 110, the UE may receive a request from the base station toreport additional information/measurement(s). The additionalinformation/measurement(s) may include (but is not limited to) locationinformation source, beam based reference signal RSRP, Reference SignalReceived Quality (RSRQ), channel impulse response, power delay profile(PDP), inertial Measurement Unit (IMU)_measurement, sensorreadings/measurements (such as barometric pressure sensor (altitude),light sensor (indoor/outdoor classification), etc. At operation 120, theUE may provide the base station with the additionalinformation/measurement(s) as per the request. At operation 130, the UEmay receive a new beam projection that is more accurate as percharacteristics of its environment and/or location.

FIG. 5 is a flow chart illustrating base station operations according tosome embodiments of inventive concepts. At operation 200, the basestation may transmit a request to the UE to report additionalinformation/measurement(s). At operation 210, the base station mayobtain (e.g., receive) the requested information/measurement(s) from theUE. At operation 220, the base station may process the input from the UEto deduce the UE environment and to identify an improved/optimum beamadjustment configuration. At operation 230, the base station may providean update of the beam configuration for the UE to a location server.

FIG. 6 is a flow chart illustrating location server operations accordingto some embodiments of inventive concepts. At block 300, the locationserver may receive the beam configuration update from the base stationand keep it (e.g., store it in memory) for future reference.

Note that some radio nodes may also have location server functionality.In such cases, some or all operations can be performed by the radio nodeitself without seeking involvement from central location server.

According to some embodiments of inventive concepts, one or more of thefollowing advantages may be provided. An improved/optimized beamadjustment strategy may be provided. More efficient RRM decisions may beprovided, such as during handover. The beam adjustment protocol may bemore sophisticated by incorporating measurements on top of conventionalbeam measurement. A beam may be projected which is better/best for theUE considering its environment. Beam projection may be improved byconsidering UE velocity and altitude. By projecting the beam away fromundesired UEs, a better data rate may be provided for the desired UE,potentially with reduced interference. Stated in other words, theprojected beam may be dedicated to a specific UE. Some embodiments ofinventive concepts, can be exploited for other applications likepositioning where the accuracy of the estimated time of arrival reliesheavily on how it is transmitted to the UE. If the reference signal forpositioning is transmitted to the UE exploiting additionalinformation/measurement, the UE may have a better opportunity to performprecise time of arrival estimation. Moreover, a UE may benefit from itsenvironment specifically tailored beam based reference signaltransmission for localization.

Some embodiments of inventive concepts may include identifying the UEEnvironment.

The additional information requested from the UE can include (but notlimited to) UE environment (indoor/outdoor), UE velocity (to identify ifa UE is moving towards or away from the base station), Line of Sight(LOS) or Non-Line of Sight (NLOS) condition of the UE with respect tothe base station, and/or UE altitude. The base station may use thisinformation together with a predefined rule to adjust the favorable beamof the UE. In some embodiments, the UE may consider more than one beamas favorable due to its certain conditions.

Some embodiments of inventive concepts may include identifying theLocation Source.

When a UE reports its location, the UE may also report its locationinformation source. The location information source can be used toidentify the UE environment such as being indoor, outdoor, in a tunnel,etc. FIG. 7 illustrates information elements that may be used tocommunicate the location information source. As shown, “a-gnss” mayindicate that the UE determined its location using an assisted globalnavigation satellite system a-GNSS (also referred to as a globalpositioning system or GPS), “wlan” may indicate that the UE determinedits location using a wireless local area network WLAN, “bt” may indicatethat the UE determined its location using Bluetooth BT signaling, “tbs”may indicate that the UE determined its location using terrestrialbeacon system positioning, “sensor” may indicate that the UE determinedits location using inertial measurement unit IMU sensors,“ha-gnss-v1510” may indicate that the UE determined its location usinghigh accuracy GNSS, and “motion-sensor-v1550” may indicate that the UEdetermined its location using motion sensors to detect displacementand/or movement (e.g., using accelerometers, gyros, magnetometers,etc.). The locationSource field of FIG. 7 may be provided in aCommonIEsProvidedLocationInformation message as discussed in 3GPP TS36.355 V15.5.0 (2019-09), cited below as Reference [2]. As discussed inReference [2], the locationSource field may provide the sourcepositioning technology used by the UE to generate the location estimate.

When the UE reports its location using an Assisted Global NavigationSatellite System (A-GNSS or HA-GNSS), then the UE is most likely in anoutdoor environment. When the UE reports its location using measurementsfrom a Wireless Local Area Network (WLAN) or from Bluetooth (BT), thenthe UE is most likely in an indoor environment. Similarly, when the UEwas using A-GNSS to report its location and has shifted to using an IMU(inertial measurement unit) sensor as location information source (e.g.,indicated by “sensor” or “motion-sensor-v1550”), then it is most likelythat the UE has entered a confined environment such as a tunnel. Besidesthis, the UE can be asked to specify more explicitly about itsenvironment information. For example, the UE can also use its lightsensor to analyze whether it is in an indoor or outdoor environment.Some UEs may also have a barometric pressure sensor which can be used todetermine/compute its height. In addition, a UE can also report itsvelocity. The UE velocity along with its elevation can helpimprove/optimize beam projection angle.

Thus, the UE may report such parameters to the gNodeB using a RadioResource Control RRC protocol. The UE may provide it's capabilitywhether it can process/identify additional parameter or not. Dependingupon UE capability, the gNodeB may fetch additional parameters from theUE.

Knowledge of an environment may be used as discussed below.

Knowledge of the UE environment may be further augmented with theknowledge of channel parameters and/or sensor readings at the UE. Onechannel characteristic which may be useful is the channel impulseresponse provided using a Power Delay Profile PDP. PDP may provide goodinformation about the environment of the UE depending on thedistribution of peaks in the PDP profile. This information can let thepeers know if they are in Line of Sight LOS or Non-Line of Sight NLOScommunication with a base station (also referred to as a radio accessnetwork RAN node). The information about this sort of propagationenvironment may further help a base station and/or UE beamformer toproject the beam to/from the peer with more accuracy.

FIG. 8A illustrates an example of a UE 801 in communication with a basestation 803 where an obstacle 805 is in a direct line of sight betweenthe UE 801 and base station 803. A first (direct) transmission path 811between the base station 803 and the UE 801 is straight but obstructedby obstacle 805, while a second (indirect) transmission path 815reflects off building 807 without obstruction. For a given downlinktransmission from base station 803 to UE 801, the downlink transmissionmay reach the UE first over the first transmission path 811 which isshorter but obstructed, and the downlink transmission may reach the UEover the second (reflected) transmission path 815 at a greater power(because obstacle 805 obstructs the first transmission path 811). Thisis illustrated in the Power Delay Profile of FIG. 8B where reception ofthe downlink transmission along the first transmission path 811 isindicated by the first peak 811′ and wherein reception of the downlinktransmission along the second transmission path 815 is indicated by thesecond peak 815′. The subsequent peaks of FIG. 8B may result from otherreflected transmission paths not shown in FIG. 8A.

The indoor/outdoor classification information and LOS/NLOS informationcan be taken as an input to determine angle, orientation, etc. of thebeam.

UE can report PDP information to the base station without solicitationor upon request from the base station. The reporting can also be madeperiodic.

According to some embodiments, the UE can report PDP information as anENUMERATED classification (LOS, NLOS) report (indicating that the UE iseither in line sight LOS communication without significant obstructionin a direct line between the UE and Base station or that the UE is innon-line of sight NLOS communication with a strongest signal beingreceived via a reflected path), or as a BIT STRING (SIZE(4)) report.With a bit string report, each bit of the bit string may represent thedelay spread sample (e.g., with each bit representing a respectivetransmission path, with 1 used to indicate the transmission path withthe strongest signal and 0 used to indicate all other transmissionpaths).

For example, the power delay profile of FIG. 9 may be represented by abit pattern of 1000 to indicate that the peak is received at the veryfirst delay spread sample (i.e., corresponding to the straight line ordirect transmission path over which the signal is first received).Accordingly, a 1000 bit pattern may indicate a LOS downlink receptionenvironment. This situation may occur by removing the obstruction 805from signal path 811 of FIG. 8A, so that the downlink transmission isreceived by UE 801 over the first transmission path 811 (now a line ofsight transmission path) with greater power than is received over thesecond (reflected) transmission path 815.

In contrast, a bit pattern of 0100 as shown in FIG. 8B may imply thatthere is no clear LOS downlink transmission (the first path is not thestrongest), but instead that the strongest reception occurs over areflected signal path or a second path as shown, for example, in FIG.8A.

UL Beam Adjustment is discussed below.

In some embodiments, the UE can also use the PDP that is available todetermine the beam projection. Similarly, the UE can use the reciprocaldirection to transmit/project its uplink beam. Stated in other words,the UE can follow the DL direction for UL beam projection.

Sending/Transmitting a Power Delay Profile is discussed below.

According to some embodiments, after obtaining the additionalmeasurement(s)/information from the UE, the base station can thenidentify a desired/optimum beam adjustment configuration for DLtransmission. The UL beam adjustment configuration can be reciprocal tothe beam adjustment configuration for the DL transmission.

According to some embodiments, the signaling between the UE and the basestation may be handled via Radio Resource Control (RRC) protocol.

Radio Resource Management RRM Decisions are discussed below.

When a UE performs mobility measurements using CSI-RS (channel stateinformation reference signals) or Positioning measurements using DL-PRS(downlink positioning reference signals), the UE is performing RSRP/RSRQ(reference signal received power and/or reference signal receivedquality) measurements of such reference signal(s). In addition, the UEalso performs Time of Arrival (TOA) estimation of such signalsespecially for DL-Positioning Reference Signal (DL-PRS). Whileestimating TOA, UE may record the earliest path of signal arrival andadditionally determine if it is in LOS with any of the neighborcells/beams. The UE may report information (e.g., PDP, UE environment,indoor/outdoor, etc.) relating to such measurements to the serving basestation. The serving base station may then decide if the UE should behanded over to the neighbor beam/cell. This is an example of how theadditional parameter can be useful for gNodeB Radio Access Network (RAN)procedures. Further, if the base station (gNodeB, also referred to as aRAN node) needs to perform carrier aggregation, it knows which cells itcan select for carrier aggregation. This information may also be usefulif gNodeB and UE may support carrier aggregation in different forms suchas intra-band contiguous or non-contiguous, or inter-band non-contiguousband combinations. Based upon the reported measurement(s) from the UEregarding different TOA and/or LOS/NLOS of different cells, the gNodeBmay select cells and can decide whether to opt for Carrier aggregationusing intraband or interband. Further, within intraband or interband,the base station may determine which of the cells are best for carrieraggregation.

According to some embodiments, the base station may determine whether toperform a handover procedure and/or may determine that a beam fromanother base station may be a more favorable beam compared to thecurrent base station's beams based on the reported additionalinformation from the UE.

According to some embodiments, the UE may also report additional beamquality information for beams received from neighbor cells (e.g., Timeof Arrival, LOS/NLOS, indoor/outdoor classification, etc.) as additionalinformation to the base station.

Reference Signal RS Beam Optimization is discussed below.

According to some embodiments, the base station can use the UE report toimprove/optimize beam transmission for reference signals such as PRS orCSI-RS. The gNodeB may have a trained Machine Learning (ML) algorithm inplace or can have an ML algorithm that can be trained with other basestations to provide beam adjustment configuration. The Xn interface canbe used to communicate for beam configuration.

The gNodeB obtains the RSRP along with additional information such asLOS/NLOS, TOA of the reference signal from each Beam. In order to selecta most appropriate (e.g., best) beam possible for providing a good QoE(Better signal reception), the gNodeB filters which beams are suitablefor UE and selects only those beams. Such an implementation may providea bona fide advantage to deterministically adjust a beam for referencesignal transmission for positioning or CSI-RS for RRM. Such animplementation may help a UE receive positioning reference signalsthrough beams that are tailored specifically based on itslocation/environment and provides/ensures precise timing measurement forlocalization and in case of RRM aid in making better mobility decisionsby selecting the appropriate CSI-RS serving and neighbor beams. Further,it may provide a mechanism to turn off beams that do not contributetowards measurement statistics such as beams which have very delayed TOAresult or which are NLOS. This may provide an energy saving mechanismfor the Network NW nodes.

According to some embodiments, the base station can forward the beamadjustment configuration along with the UE reported additionalinformation/measurement(s) to a higher layer entity such as a Locationand Mobility Function (LMF) node. The LMF node may have a trainedMachine Learning (ML) algorithm in place, or the LMF node may have an MLalgorithm that can be trained with the base station provided beamadjustment configuration along with the UE reported additionalinformation/measurement. Such embodiments may provide an advantage todeterministically adjust a beam for reference signal transmission forpositioning. Such an implementation may help the UE to receivepositioning reference signals through beams that are tailoredspecifically based on the UE's location/environment and toprovide/ensure precise timing measurement for localization. To handlethis sort of information exchange, the signaling between the basestation and the LMF node may be handled using Long Term PositioningProtocol-a (LPPa) or New Radio Positioning Protocol-a (NRPPa) protocol.

Beam Adjustment is discussed below.

According to some embodiments, the base station may perform a table lookup operation to identify a desired/optimum beam adjustmentconfiguration/parameter.

The beam adjustment configuration may be one of the following: Transmitor receive beam direction; Time and/or frequency resources or schedulinginformation for beam-associated transmissions; Transmit or receive beamwidth; Power boosting for beam-specific transmissions; and/or AdaptiveBeam (UE specific beams). Beam association information (or rule(s)),e.g., association between network transmit beam and UE receive beam,association between network transmit and network receive beam, orassociation between UE transmit beam and UE receive beam, is illustratedin the table of FIG. 10A.

The look up table in its normative form may be provided as shown by thetable of FIG. 10B.

As an example, if the UE is in a NLOS condition but is outdoors, thebeam projection can be determined by the serving gNodeB based on thebest path direction to reach UE with increased/maximum signal strength.This can be done by combining an optimum higher number of antennaelements to derive a narrow beam pointing towards the angle of departurewhere the UE has perceived highest/maximum RSRP value or the path amongthe multiple paths where the RSRP value is highest. Moreover, based onthe additional info, a UE that is in LOS and outdoors can also be fairlyidentified by the serving cell. Upon identification of such a condition,the gNodeB can then project an improved/optimized beam only to servethis UE to reduce/minimize the interference to other UEs. In an outdooronly deployment scenario, where all gNodeBs are deployed outdoors and nogNodeB is deployed indoors, the gNodeB can also identify if a UE is inNLOS and indoor based on the additional measurement reported by the UE.In such a situation, the outdoor gNodeB can project the beam to overcomeadditional pathloss of the signal due wall blockage and can serve theindoor UE with better coverage. In this aspect, the serving cell inaddition to the additional measurement reported by UE can also measurepathloss of the UL signal coming from UE to adjust its transmissionpower. Moreover, based on the estimated angle of arrival, the servingcell can project its beam/beams. In a deployment where gNodeBs are alsodeployed indoors, the beam projection can be fairly improved/optimizedby the serving cell depending on the LOS and NLOS condition of the UEwith the serving cell. The additional information in this context canalso help to better position measurements typically used/required tolocalize the UE with precision.

An example of Info/measurement type 1 is where UE is located outdoor orindoor. The Value1 corresponding to this measurement type can be indoor.

An example of Info/measurement type 2 is NLOS/LOS. The Value1corresponding to this measurement type can be NLOS.

An example of Info/measurement type 3 is TOA. The Value1 correspondingto this measurement type can be in time duration such as ns,microsecond, millisecond.

Based upon this, the beam may be adjusted. For example, the beamadjustment may include one or more of: Transmit or receive beamdirection; Time and/or frequency resources or scheduling information forbeam-associated transmissions; Transmit or receive beam width; Powerboosting for beam-specific transmissions; and/or Adaptive Beam (UEspecific beams, selection of beams). This adjustment may happenperiodically over certain TTI, for example, based upon the correspondingvalue 2, value 3 etc.

Some embodiments of inventive concepts may thus provide more efficientbeam adjustment/alignment.

Operations of a RAN node 400 (implemented using the structure of FIG. 12) will now be discussed with reference to the flow chart of FIG. 14according to some embodiments of inventive concepts. For example,modules may be stored in memory 405 of FIG. 12 , and these modules mayprovide instructions so that when the instructions of a module areexecuted by respective RAN node processing circuitry 403, processingcircuitry 403 performs respective operations of the flow chart.

At block 1401, processing circuitry 403 may obtain information definingan operational environment in which a wireless device is operating.

At block 1405, processing circuitry 403 may manage communication withthe wireless device based on the information defining the operationalenvironment in which the wireless device is operating.

The information defining the operational environment may include anindication that the wireless device is in line of sight LOS or non-lineof sight NLOS communication with the RAN node. For example, obtainingthe information defining the operational environment may includereceiving (through transceiver 401) the indication that the wirelessdevice in LOS or NLOS communication with the RAN node from the wirelessdevice. In addition or in an alternative, obtaining the informationdefining the operational environment may include receiving (throughtransceiver 401) a representation of a power delay profile PDP from thewireless device, and determining the indication based on therepresentation of the PDP.

The information defining the operational environment may include anindication that the wireless device is indoors, semi-indoors, oroutdoors.

Obtaining the information defining the operational environment mayinclude receiving (through transceiver 401) an identification of alocation information source from the wireless device identifying asource used by the wireless device to determine a location of thewireless device and determining whether the wireless device is indoors,semi-indoors, or outdoors based on the identification of the locationinformation source. The identification of the location informationsource may identify a global navigation satellite system GNSS source andthe wireless device may be determined to be outdoors based onidentification of the GNSS source. The identification of the locationinformation source may identify a wireless local area network WLANsource and/or a Bluetooth BT source, and the wireless device may bedetermined to be indoors based on identification of the WLAN sourceand/or the BT source.

Obtaining the information defining the operational environment mayinclude receiving (through transceiver 401) the indication that thewireless device is indoors, semi-indoors, or outdoors from the wirelessdevice.

Obtaining the information defining the operational environment mayinclude receiving (through transceiver 401) a light sensor measurementfrom the wireless device and determining whether the wireless device isindoors, semi-indoors, or outdoors based on the light sensormeasurement.

Obtaining the information defining the operational environment mayinclude receiving (through transceiver 401) an indication from thewireless device that a inertial sensor is used to provide locationinformation for the wireless device and determining that the wirelessdevice is in a confined space based on the indication that the inertialsensor is used to provide location information, and the communicationwith the wireless device may be managed based on determining that thewireless device is in a confined space.

Obtaining the information defining the operational environment mayinclude receiving (through transceiver 401) time of arrival TOAinformation for a signal received at the wireless device, wherein theTOA information is received from the wireless device, and thecommunication may be managed based on the TOA information received fromthe wireless device.

Various operations from the flow chart of FIG. 14 may be optional withrespect to some embodiments of RAN nodes and related methods.

Operations of a RAN node 400 (implemented using the structure of FIG. 12) will now be discussed with reference to the flow chart of FIG. 15according to some embodiments of inventive concepts. For example,modules may be stored in memory 405 of FIG. 4 , and these modules mayprovide instructions so that when the instructions of a module areexecuted by respective RAN node processing circuitry 403, processingcircuitry 403 performs respective operations of the flow chart.

At block 1401, processing circuitry 403 may obtain information definingan operational environment in which a wireless device is operating.

At block 1503, processing circuitry may receive (through transceiver401) a measurement of received signal quality and/or received signalpower from the wireless device, with the measurement being a measurementof the received signal quality and/or the received signal power at thewireless device. For example, the received signal quality and/or thereceived signal power may be for at least one beam received by thewireless device from the RAN node. Moreover, the received signal qualityand/or the received signal power may include a Reference Signal ReceivedQuality RSRQ and/or a Reference Signal Received Power RSRP.

At block 1505, processing circuitry 403 may manage communication withthe wireless device based on the information defining the operationalenvironment in which the wireless device is operating and/or based onthe measurement of the received signal quality and/or the receivedsignal power

Various operations from the flow chart of FIG. 15 may be optional withrespect to some embodiments of RAN nodes and related methods. Forexample, operations of block 1503 of FIG. 15 may be optional accordingto some embodiments.

Operations of a RAN node 400 (implemented using the structure of FIG. 12) will now be discussed with reference to the flow charts of FIGS. 16Aand 16B according to some embodiments of inventive concepts. Forexample, modules may be stored in memory 405 of FIG. 12 , and thesemodules may provide instructions so that when the instructions of amodule are executed by respective RAN node processing circuitry 403,processing circuitry 403 performs respective operations of the flowchart.

At block 1401, processing circuitry 403 may obtain information definingan operational environment in which a wireless device is operating.

At block 1503, processing circuitry 403 may receive (through transceiver403) a measurement of received signal quality and/or received signalpower from the wireless device, wherein the measurement is a measurementof the received signal quality and/or the received signal power at thewireless device.

At block 1605, processing circuitry 403 may manage communication withthe wireless device by performing beam management for the wirelessdevice based on the information defining the operational environment inwhich the wireless device is operating and/or based on the measurementof the received signal quality and/or the received signal power.

For example, performing beam management may include performing beamadjustment and/or beam alignment for the wireless device based on theinformation defining the operation environment in which the wirelessdevice is operating and/or based on the measurement of the receivedsignal quality and/or received signal power. In addition or in analternative, performing beam management may include selecting (at block1605A) a beam for communication with the wireless device based on theinformation defining the operational environment in which the wirelessdevice is operating and/or based on the measurement of the receivessignal quality and/or the received power, and communicating (at block1605B, e.g., transmitting and/or receiving) data with the wirelessdevice (through transceiver 401) using the beam selected forcommunication with the wireless device.

Various operations from the flow chart of FIGS. 16A and 16B may beoptional with respect to some embodiments of RAN nodes and relatedmethods. For example, operations of blocks 1503, 1605A, and/or 1605B ofFIGS. 16A and/or 16B may be optional according to some embodiments.

Operations of a RAN node 400 (implemented using the structure of FIG. 12) will now be discussed with reference to the flow chart of FIG. 17according to some embodiments of inventive concepts. For example,modules may be stored in memory 405 of FIG. 12 , and these modules mayprovide instructions so that when the instructions of a module areexecuted by respective RAN node processing circuitry 403, processingcircuitry 403 performs respective operations of the flow chart.

At block 1401, processing circuitry 403 may obtain information definingan operational environment in which a wireless device is operating.

At block 1503, processing circuitry 403 may receive (through transceiver401) a measurement of received signal quality and/or received signalpower from the wireless device, wherein the measurement is a measurementof the received signal quality and/or the received signal power at thewireless device, and wherein communication with the wireless device ismanaged based on the information defining the operational environment inwhich the wireless device is operating and/or based on the measurementof the received signal quality and/or the received signal power.

At block 1705, processing circuitry 403 may manage communication withthe wireless device by performing a handover of the wireless device fromthe RAN node to another RAN node based on the information defining theoperational environment in which the wireless device is operating and/orbased on the measurement of the received signal quality and/or thereceived signal power.

Various operations from the flow chart of FIG. 17 may be optional withrespect to some embodiments of RAN nodes and related methods. Forexample, operations of block 1503 of FIG. 17 may be optional accordingto some embodiments.

Operations of a RAN node 400 (implemented using the structure of FIG. 12) will now be discussed with reference to the flow chart of FIG. 18according to some embodiments of inventive concepts. For example,modules may be stored in memory 405 of FIG. 12 , and these modules mayprovide instructions so that when the instructions of a module areexecuted by respective RAN node processing circuitry 403, processingcircuitry 403 performs respective operations of the flow chart.

At block 1401, processing circuitry 403 may obtain information definingan operational environment in which a wireless device is operating.

At block 1503, processing circuitry 403 may receive (through transceiver401) a measurement of received signal quality and/or received signalpower from the wireless device, wherein the measurement is a measurementof the received signal quality and/or the received signal power at thewireless device, and wherein communication with the wireless device ismanaged based on the information defining the operational environment inwhich the wireless device is operating and/or based on the measurementof the received signal quality and/or the received signal power.

At block 1805, processing circuitry 403 may manage communication withthe wireless device by performing carrier aggregation for the wirelessdevice based on the information defining the operational environment inwhich the wireless device is operating and/or based on the measurementof the received signal quality and/or the received signal power. Forexample, performing carrier aggregation at block 1805 may includeselecting (at block 1805A) at least one component carrier to providecarrier aggregation for the wireless device, and communicating (at block1805B) data with the wireless device (e.g., transmitting and/orreceiving through transceiver 401) using the at least one componentcarrier selected to provide carrier aggregation.

Various operations from the flow charts of FIGS. 18A and/or 18B may beoptional with respect to some embodiments of RAN nodes and relatedmethods. For example, operations of block 1503, 1805A, and/or 1805B ofFIGS. 18A and/or 18B may be optional according to some embodiments.

Operations of a RAN node 400 (implemented using the structure of FIG. 12) will now be discussed with reference to the flow chart of FIG. 19according to some embodiments of inventive concepts. For example,modules may be stored in memory 405 of FIG. 12 , and these modules mayprovide instructions so that when the instructions of a module areexecuted by respective RAN node processing circuitry 403, processingcircuitry 403 performs respective operations of the flow chart.

At block 1401, processing circuitry 403 may obtain information definingan operational environment in which a wireless device is operating;

At block 1503, processing circuitry 403 may receive a measurement ofreceived signal quality and/or received signal power from the wirelessdevice, wherein the measurement is a measurement of the received signalquality and/or the received signal power at the wireless device.

At block 1905, processing circuitry 403 may manage communication withthe wireless device by controlling transmission of a reference signalbased on the information defining the operational environment in whichthe wireless device is operating and/or based on the measurement of thereceived signal quality and/or the received signal power.

For example, controlling transmission may include selecting (at block1095A) a beam for the reference signal based on the information definingthe operational environment in which the wireless device is operatingand/or based on the measurement of the received signal quality and/orthe received signal power, and transmitting (at block 1905B) thereference signal (through transceiver 401) using the beam selected forthe reference signal. Moreover, the reference signal may include atleast one of a positioning reference signal PRS, a channel stateinformation reference signal CSI-RS, and/or cell specific referencesignal CRS.

Various operations from the flow charts of FIGS. 19A and/or 19B may beoptional with respect to some embodiments of RAN nodes and relatedmethods. For example, operations of block 1503, 1905A, and/or 1905B ofFIGS. 19A and/or 19B may be optional according to some embodiments.

At block 1401, processing circuitry 403 may obtain information definingan operational environment in which a wireless device is operating.

At block 2001, processing circuitry 403 may obtain information for aplurality of beams. The information for the plurality of beams may beobtained by receiving (through transceiver 401) the information from thewireless device, and the information for the plurality of beams mayinclude a received signal quality and/or a received signal power foreach of the plurality of beams. For example, the received signal qualityand/or the received signal power may include a Reference Signal ReceivedQuality, RSRQ, and/or a Reference Signal Received Power, RSRP for eachof the plurality of beams.

At block 2005 processing circuitry 403 may manage communication with thewireless device by selecting a beam from the plurality of beams based onthe information defining the operational environment in which thewireless device is operating and/or based on the information for theplurality of beams.

At block 2009, processing circuitry 403 may communicate (e.g., transmitand/or receive) data with the wireless device (through transceiver)using the beam selected for communication with the wireless device.

Various operations from the flow charts of FIG. 20 may be optional withrespect to some embodiments of RAN nodes and related methods. Forexample, operations of blocks 2001 and/or 2009 of FIG. 20 may beoptional according to some embodiments.

Explanations are provided below for various abbreviations/acronyms usedin the present disclosure.

Abbreviation Explanation NR New Radio OTDOA Observed Time Difference ofArrival PDP Power Delay Profile LOS Line of Sight NLOS Non-Line of SightTDOA Time Difference of Arrival IMU Inertial Motion Unit RSRP ReferenceSignal Received Power RSRQ Reference Signal Received Quality UE UserEquipment LPPa LTE Positioning Protocol-a NRPPa New Radio PositioningProtocol-a TOA Time of Arrival RAN Radio Access Network RS ReferenceSignal BS Base Station UL Uplink DL Downlink RF Radio Frequency LMFLocation and Mobility Function AMF Access and Mobility managementFunction E-SMLC Evolved Serving Mobile Location Centre NG NextGeneration GPS Global Positioning System RRM Radio Resource ManagementA-GNSS Assisted Global Navigation Satellite System BT BlueTooth WLANWireless Local Area Network RRC Radio Resource Control PRS PositioningReference Signal ML Machine Learning 5G 5^(th) Generation QoE Quality ofExperience

References are identified below.

-   Reference [1] U.S. Pat. No. 6,512,481, to Velazquez et al., entitled    “Communication System Using Geographic Position Data,” issued Jan.    28, 2003.-   Reference [2] 3GPP TS 36.355 V15.5.0 (2019 September), Technical    Specification Group Radio Access Network, Evolved Universal    Terrestrial Radio Access (E-UTRA): LTE Positioning Protocol (LPP)    (Release 15)

Additional explanation is provided below.

Generally, all terms used herein are to be interpreted according totheir ordinary meaning in the relevant technical field, unless adifferent meaning is clearly given and/or is implied from the context inwhich it is used. All references to a/an/the element, apparatus,component, means, step, etc. are to be interpreted openly as referringto at least one instance of the element, apparatus, component, means,step, etc., unless explicitly stated otherwise. The steps of any methodsdisclosed herein do not have to be performed in the exact orderdisclosed, unless a step is explicitly described as following orpreceding another step and/or where it is implicit that a step mustfollow or precede another step. Any feature of any of the embodimentsdisclosed herein may be applied to any other embodiment, whereverappropriate. Likewise, any advantage of any of the embodiments may applyto any other embodiments, and vice versa. Other objectives, features andadvantages of the enclosed embodiments will be apparent from thefollowing description.

Some of the embodiments contemplated herein will now be described morefully with reference to the accompanying drawings. Other embodiments,however, are contained within the scope of the subject matter disclosedherein, the disclosed subject matter should not be construed as limitedto only the embodiments set forth herein; rather, these embodiments areprovided by way of example to convey the scope of the subject matter tothose skilled in the art.

FIG. 21 illustrates a wireless network in accordance with someembodiments.

Although the subject matter described herein may be implemented in anyappropriate type of system using any suitable components, theembodiments disclosed herein are described in relation to a wirelessnetwork, such as the example wireless network illustrated in FIG. 21 .For simplicity, the wireless network of FIG. 21 only depicts network4106, network nodes 4160 and 4160 b, and WDs 4110, 4110 b, and 4110 c(also referred to as mobile terminals). In practice, a wireless networkmay further include any additional elements suitable to supportcommunication between wireless devices or between a wireless device andanother communication device, such as a landline telephone, a serviceprovider, or any other network node or end device. Of the illustratedcomponents, network node 4160 and wireless device (WD) 4110 are depictedwith additional detail. The wireless network may provide communicationand other types of services to one or more wireless devices tofacilitate the wireless devices' access to and/or use of the servicesprovided by, or via, the wireless network.

The wireless network may comprise and/or interface with any type ofcommunication, telecommunication, data, cellular, and/or radio networkor other similar type of system. In some embodiments, the wirelessnetwork may be configured to operate according to specific standards orother types of predefined rules or procedures. Thus, particularembodiments of the wireless network may implement communicationstandards, such as Global System for Mobile Communications (GSM),Universal Mobile Telecommunications System (UMTS), Long Term Evolution(LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless localarea network (WLAN) standards, such as the IEEE 802.11 standards; and/orany other appropriate wireless communication standard, such as theWorldwide Interoperability for Microwave Access (WiMax), Bluetooth,Z-Wave and/or ZigBee standards.

Network 4106 may comprise one or more backhaul networks, core networks,IP networks, public switched telephone networks (PSTNs), packet datanetworks, optical networks, wide-area networks (WANs), local areanetworks (LANs), wireless local area networks (WLANs), wired networks,wireless networks, metropolitan area networks, and other networks toenable communication between devices.

Network node 4160 and WD 4110 comprise various components described inmore detail below. These components work together in order to providenetwork node and/or wireless device functionality, such as providingwireless connections in a wireless network. In different embodiments,the wireless network may comprise any number of wired or wirelessnetworks, network nodes, base stations, controllers, wireless devices,relay stations, and/or any other components or systems that mayfacilitate or participate in the communication of data and/or signalswhether via wired or wireless connections.

As used herein, network node refers to equipment capable, configured,arranged and/or operable to communicate directly or indirectly with awireless device and/or with other network nodes or equipment in thewireless network to enable and/or provide wireless access to thewireless device and/or to perform other functions (e.g., administration)in the wireless network. Examples of network nodes include, but are notlimited to, access points (APs) (e.g., radio access points), basestations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs(eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based onthe amount of coverage they provide (or, stated differently, theirtransmit power level) and may then also be referred to as femto basestations, pico base stations, micro base stations, or macro basestations. A base station may be a relay node or a relay donor nodecontrolling a relay. A network node may also include one or more (orall) parts of a distributed radio base station such as centralizeddigital units and/or remote radio units (RRUs), sometimes referred to asRemote Radio Heads (RRHs). Such remote radio units may or may not beintegrated with an antenna as an antenna integrated radio. Parts of adistributed radio base station may also be referred to as nodes in adistributed antenna system (DAS). Yet further examples of network nodesinclude multi-standard radio (MSR) equipment such as MSR BSs, networkcontrollers such as radio network controllers (RNCs) or base stationcontrollers (BSCs), base transceiver stations (BTSs), transmissionpoints, transmission nodes, multi-cell/multicast coordination entities(MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SONnodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As anotherexample, a network node may be a virtual network node as described inmore detail below. More generally, however, network nodes may representany suitable device (or group of devices) capable, configured, arranged,and/or operable to enable and/or provide a wireless device with accessto the wireless network or to provide some service to a wireless devicethat has accessed the wireless network.

In FIG. 21 , network node 4160 includes processing circuitry 4170,device readable medium 4180, interface 4190, auxiliary equipment 4184,power source 4186, power circuitry 4187, and antenna 4162. Althoughnetwork node 4160 illustrated in the example wireless network of FIG. 21may represent a device that includes the illustrated combination ofhardware components, other embodiments may comprise network nodes withdifferent combinations of components. It is to be understood that anetwork node comprises any suitable combination of hardware and/orsoftware needed to perform the tasks, features, functions and methodsdisclosed herein. Moreover, while the components of network node 4160are depicted as single boxes located within a larger box, or nestedwithin multiple boxes, in practice, a network node may comprise multipledifferent physical components that make up a single illustratedcomponent (e.g., device readable medium 4180 may comprise multipleseparate hard drives as well as multiple RAM modules).

Similarly, network node 4160 may be composed of multiple physicallyseparate components (e.g., a NodeB component and a RNC component, or aBTS component and a BSC component, etc.), which may each have their ownrespective components. In certain scenarios in which network node 4160comprises multiple separate components (e.g., BTS and BSC components),one or more of the separate components may be shared among severalnetwork nodes. For example, a single RNC may control multiple NodeB's.In such a scenario, each unique NodeB and RNC pair, may in someinstances be considered a single separate network node. In someembodiments, network node 4160 may be configured to support multipleradio access technologies (RATs). In such embodiments, some componentsmay be duplicated (e.g., separate device readable medium 4180 for thedifferent RATs) and some components may be reused (e.g., the sameantenna 4162 may be shared by the RATs). Network node 4160 may alsoinclude multiple sets of the various illustrated components fordifferent wireless technologies integrated into network node 4160, suchas, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wirelesstechnologies. These wireless technologies may be integrated into thesame or different chip or set of chips and other components withinnetwork node 4160.

Processing circuitry 4170 is configured to perform any determining,calculating, or similar operations (e.g., certain obtaining operations)described herein as being provided by a network node. These operationsperformed by processing circuitry 4170 may include processinginformation obtained by processing circuitry 4170 by, for example,converting the obtained information into other information, comparingthe obtained information or converted information to information storedin the network node, and/or performing one or more operations based onthe obtained information or converted information, and as a result ofsaid processing making a determination.

Processing circuitry 4170 may comprise a combination of one or more of amicroprocessor, controller, microcontroller, central processing unit,digital signal processor, application-specific integrated circuit, fieldprogrammable gate array, or any other suitable computing device,resource, or combination of hardware, software and/or encoded logicoperable to provide, either alone or in conjunction with other networknode 4160 components, such as device readable medium 4180, network node4160 functionality. For example, processing circuitry 4170 may executeinstructions stored in device readable medium 4180 or in memory withinprocessing circuitry 4170. Such functionality may include providing anyof the various wireless features, functions, or benefits discussedherein. In some embodiments, processing circuitry 4170 may include asystem on a chip (SOC).

In some embodiments, processing circuitry 4170 may include one or moreof radio frequency (RF) transceiver circuitry 4172 and basebandprocessing circuitry 4174. In some embodiments, radio frequency (RF)transceiver circuitry 4172 and baseband processing circuitry 4174 may beon separate chips (or sets of chips), boards, or units, such as radiounits and digital units. In alternative embodiments, part or all of RFtransceiver circuitry 4172 and baseband processing circuitry 4174 may beon the same chip or set of chips, boards, or units

In certain embodiments, some or all of the functionality describedherein as being provided by a network node, base station, eNB or othersuch network device may be performed by processing circuitry 4170executing instructions stored on device readable medium 4180 or memorywithin processing circuitry 4170. In alternative embodiments, some orall of the functionality may be provided by processing circuitry 4170without executing instructions stored on a separate or discrete devicereadable medium, such as in a hard-wired manner. In any of thoseembodiments, whether executing instructions stored on a device readablestorage medium or not, processing circuitry 4170 can be configured toperform the described functionality. The benefits provided by suchfunctionality are not limited to processing circuitry 4170 alone or toother components of network node 4160, but are enjoyed by network node4160 as a whole, and/or by end users and the wireless network generally.

Device readable medium 4180 may comprise any form of volatile ornon-volatile computer readable memory including, without limitation,persistent storage, solid-state memory, remotely mounted memory,magnetic media, optical media, random access memory (RAM), read-onlymemory (ROM), mass storage media (for example, a hard disk), removablestorage media (for example, a flash drive, a Compact Disk (CD) or aDigital Video Disk (DVD)), and/or any other volatile or non-volatile,non-transitory device readable and/or computer-executable memory devicesthat store information, data, and/or instructions that may be used byprocessing circuitry 4170. Device readable medium 4180 may store anysuitable instructions, data or information, including a computerprogram, software, an application including one or more of logic, rules,code, tables, etc. and/or other instructions capable of being executedby processing circuitry 4170 and, utilized by network node 4160. Devicereadable medium 4180 may be used to store any calculations made byprocessing circuitry 4170 and/or any data received via interface 4190.In some embodiments, processing circuitry 4170 and device readablemedium 4180 may be considered to be integrated.

Interface 4190 is used in the wired or wireless communication ofsignalling and/or data between network node 4160, network 4106, and/orWDs 4110. As illustrated, interface 4190 comprises port(s)/terminal(s)4194 to send and receive data, for example to and from network 4106 overa wired connection. Interface 4190 also includes radio front endcircuitry 4192 that may be coupled to, or in certain embodiments a partof, antenna 4162. Radio front end circuitry 4192 comprises filters 4198and amplifiers 4196. Radio front end circuitry 4192 may be connected toantenna 4162 and processing circuitry 4170. Radio front end circuitrymay be configured to condition signals communicated between antenna 4162and processing circuitry 4170. Radio front end circuitry 4192 mayreceive digital data that is to be sent out to other network nodes orWDs via a wireless connection. Radio front end circuitry 4192 mayconvert the digital data into a radio signal having the appropriatechannel and bandwidth parameters using a combination of filters 4198and/or amplifiers 4196. The radio signal may then be transmitted viaantenna 4162. Similarly, when receiving data, antenna 4162 may collectradio signals which are then converted into digital data by radio frontend circuitry 4192. The digital data may be passed to processingcircuitry 4170. In other embodiments, the interface may comprisedifferent components and/or different combinations of components.

In certain alternative embodiments, network node 4160 may not includeseparate radio front end circuitry 4192, instead, processing circuitry4170 may comprise radio front end circuitry and may be connected toantenna 4162 without separate radio front end circuitry 4192. Similarly,in some embodiments, all or some of RF transceiver circuitry 4172 may beconsidered a part of interface 4190. In still other embodiments,interface 4190 may include one or more ports or terminals 4194, radiofront end circuitry 4192, and RF transceiver circuitry 4172, as part ofa radio unit (not shown), and interface 4190 may communicate withbaseband processing circuitry 4174, which is part of a digital unit (notshown).

Antenna 4162 may include one or more antennas, or antenna arrays,configured to send and/or receive wireless signals. Antenna 4162 may becoupled to radio front end circuitry 4190 and may be any type of antennacapable of transmitting and receiving data and/or signals wirelessly. Insome embodiments, antenna 4162 may comprise one or moreomni-directional, sector or panel antennas operable to transmit/receiveradio signals between, for example, 2 GHz and 66 GHz. Anomni-directional antenna may be used to transmit/receive radio signalsin any direction, a sector antenna may be used to transmit/receive radiosignals from devices within a particular area, and a panel antenna maybe a line of sight antenna used to transmit/receive radio signals in arelatively straight line. In some instances, the use of more than oneantenna may be referred to as MIMO. In certain embodiments, antenna 4162may be separate from network node 4160 and may be connectable to networknode 4160 through an interface or port.

Antenna 4162, interface 4190, and/or processing circuitry 4170 may beconfigured to perform any receiving operations and/or certain obtainingoperations described herein as being performed by a network node. Anyinformation, data and/or signals may be received from a wireless device,another network node and/or any other network equipment. Similarly,antenna 4162, interface 4190, and/or processing circuitry 4170 may beconfigured to perform any transmitting operations described herein asbeing performed by a network node. Any information, data and/or signalsmay be transmitted to a wireless device, another network node and/or anyother network equipment.

Power circuitry 4187 may comprise, or be coupled to, power managementcircuitry and is configured to supply the components of network node4160 with power for performing the functionality described herein. Powercircuitry 4187 may receive power from power source 4186. Power source4186 and/or power circuitry 4187 may be configured to provide power tothe various components of network node 4160 in a form suitable for therespective components (e.g., at a voltage and current level needed foreach respective component). Power source 4186 may either be included in,or external to, power circuitry 4187 and/or network node 4160. Forexample, network node 4160 may be connectable to an external powersource (e.g., an electricity outlet) via an input circuitry or interfacesuch as an electrical cable, whereby the external power source suppliespower to power circuitry 4187. As a further example, power source 4186may comprise a source of power in the form of a battery or battery packwhich is connected to, or integrated in, power circuitry 4187. Thebattery may provide backup power should the external power source fail.Other types of power sources, such as photovoltaic devices, may also beused.

Alternative embodiments of network node 4160 may include additionalcomponents beyond those shown in FIG. 21 that may be responsible forproviding certain aspects of the network node's functionality, includingany of the functionality described herein and/or any functionalitynecessary to support the subject matter described herein. For example,network node 4160 may include user interface equipment to allow input ofinformation into network node 4160 and to allow output of informationfrom network node 4160. This may allow a user to perform diagnostic,maintenance, repair, and other administrative functions for network node4160.

As used herein, wireless device (WD) refers to a device capable,configured, arranged and/or operable to communicate wirelessly withnetwork nodes and/or other wireless devices. Unless otherwise noted, theterm WD may be used interchangeably herein with user equipment (UE).Communicating wirelessly may involve transmitting and/or receivingwireless signals using electromagnetic waves, radio waves, infraredwaves, and/or other types of signals suitable for conveying informationthrough air. In some embodiments, a WD may be configured to transmitand/or receive information without direct human interaction. Forinstance, a WD may be designed to transmit information to a network on apredetermined schedule, when triggered by an internal or external event,or in response to requests from the network. Examples of a WD include,but are not limited to, a smart phone, a mobile phone, a cell phone, avoice over IP (VoIP) phone, a wireless local loop phone, a desktopcomputer, a personal digital assistant (PDA), a wireless cameras, agaming console or device, a music storage device, a playback appliance,a wearable terminal device, a wireless endpoint, a mobile station, atablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mountedequipment (LME), a smart device, a wireless customer-premise equipment(CPE). a vehicle-mounted wireless terminal device, etc. A WD may supportdevice-to-device (D2D) communication, for example by implementing a 3GPPstandard for sidelink communication, vehicle-to-vehicle (V2V),vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may inthis case be referred to as a D2D communication device. As yet anotherspecific example, in an Internet of Things (IoT) scenario, a WD mayrepresent a machine or other device that performs monitoring and/ormeasurements, and transmits the results of such monitoring and/ormeasurements to another WD and/or a network node. The WD may in thiscase be a machine-to-machine (M2M) device, which may in a 3GPP contextbe referred to as an MTC device. As one particular example, the WD maybe a UE implementing the 3GPP narrow band internet of things (NB-IoT)standard. Particular examples of such machines or devices are sensors,metering devices such as power meters, industrial machinery, or home orpersonal appliances (e.g. refrigerators, televisions, etc.) personalwearables (e.g., watches, fitness trackers, etc.). In other scenarios, aWD may represent a vehicle or other equipment that is capable ofmonitoring and/or reporting on its operational status or other functionsassociated with its operation. A WD as described above may represent theendpoint of a wireless connection, in which case the device may bereferred to as a wireless terminal. Furthermore, a WD as described abovemay be mobile, in which case it may also be referred to as a mobiledevice or a mobile terminal.

As illustrated, wireless device 4110 includes antenna 4111, interface4114, processing circuitry 4120, device readable medium 4130, userinterface equipment 4132, auxiliary equipment 4134, power source 4136and power circuitry 4137. WD 4110 may include multiple sets of one ormore of the illustrated components for different wireless technologiessupported by WD 4110, such as, for example, GSM, WCDMA, LTE, NR, WiFi,WiMAX, or Bluetooth wireless technologies, just to mention a few. Thesewireless technologies may be integrated into the same or different chipsor set of chips as other components within WD 4110.

Antenna 4111 may include one or more antennas or antenna arrays,configured to send and/or receive wireless signals, and is connected tointerface 4114. In certain alternative embodiments, antenna 4111 may beseparate from WD 4110 and be connectable to WD 4110 through an interfaceor port. Antenna 4111, interface 4114, and/or processing circuitry 4120may be configured to perform any receiving or transmitting operationsdescribed herein as being performed by a WD. Any information, dataand/or signals may be received from a network node and/or another WD. Insome embodiments, radio front end circuitry and/or antenna 4111 may beconsidered an interface.

As illustrated, interface 4114 comprises radio front end circuitry 4112and antenna 4111. Radio front end circuitry 4112 comprise one or morefilters 4118 and amplifiers 4116. Radio front end circuitry 4114 isconnected to antenna 4111 and processing circuitry 4120, and isconfigured to condition signals communicated between antenna 4111 andprocessing circuitry 4120. Radio front end circuitry 4112 may be coupledto or a part of antenna 4111. In some embodiments, WD 4110 may notinclude separate radio front end circuitry 4112; rather, processingcircuitry 4120 may comprise radio front end circuitry and may beconnected to antenna 4111. Similarly, in some embodiments, some or allof RF transceiver circuitry 4122 may be considered a part of interface4114. Radio front end circuitry 4112 may receive digital data that is tobe sent out to other network nodes or WDs via a wireless connection.Radio front end circuitry 4112 may convert the digital data into a radiosignal having the appropriate channel and bandwidth parameters using acombination of filters 4118 and/or amplifiers 4116. The radio signal maythen be transmitted via antenna 4111. Similarly, when receiving data,antenna 4111 may collect radio signals which are then converted intodigital data by radio front end circuitry 4112. The digital data may bepassed to processing circuitry 4120. In other embodiments, the interfacemay comprise different components and/or different combinations ofcomponents.

Processing circuitry 4120 may comprise a combination of one or more of amicroprocessor, controller, microcontroller, central processing unit,digital signal processor, application-specific integrated circuit, fieldprogrammable gate array, or any other suitable computing device,resource, or combination of hardware, software, and/or encoded logicoperable to provide, either alone or in conjunction with other WD 4110components, such as device readable medium 4130, WD 4110 functionality.Such functionality may include providing any of the various wirelessfeatures or benefits discussed herein. For example, processing circuitry4120 may execute instructions stored in device readable medium 4130 orin memory within processing circuitry 4120 to provide the functionalitydisclosed herein.

As illustrated, processing circuitry 4120 includes one or more of RFtransceiver circuitry 4122, baseband processing circuitry 4124, andapplication processing circuitry 4126. In other embodiments, theprocessing circuitry may comprise different components and/or differentcombinations of components. In certain embodiments processing circuitry4120 of WD 4110 may comprise a SOC. In some embodiments, RF transceivercircuitry 4122, baseband processing circuitry 4124, and applicationprocessing circuitry 4126 may be on separate chips or sets of chips. Inalternative embodiments, part or all of baseband processing circuitry4124 and application processing circuitry 4126 may be combined into onechip or set of chips, and RF transceiver circuitry 4122 may be on aseparate chip or set of chips. In still alternative embodiments, part orall of RF transceiver circuitry 4122 and baseband processing circuitry4124 may be on the same chip or set of chips, and application processingcircuitry 4126 may be on a separate chip or set of chips. In yet otheralternative embodiments, part or all of RF transceiver circuitry 4122,baseband processing circuitry 4124, and application processing circuitry4126 may be combined in the same chip or set of chips. In someembodiments, RF transceiver circuitry 4122 may be a part of interface4114. RF transceiver circuitry 4122 may condition RF signals forprocessing circuitry 4120.

In certain embodiments, some or all of the functionality describedherein as being performed by a WD may be provided by processingcircuitry 4120 executing instructions stored on device readable medium4130, which in certain embodiments may be a computer-readable storagemedium. In alternative embodiments, some or all of the functionality maybe provided by processing circuitry 4120 without executing instructionsstored on a separate or discrete device readable storage medium, such asin a hard-wired manner. In any of those particular embodiments, whetherexecuting instructions stored on a device readable storage medium ornot, processing circuitry 4120 can be configured to perform thedescribed functionality. The benefits provided by such functionality arenot limited to processing circuitry 4120 alone or to other components ofWD 4110, but are enjoyed by WD 4110 as a whole, and/or by end users andthe wireless network generally.

Processing circuitry 4120 may be configured to perform any determining,calculating, or similar operations (e.g., certain obtaining operations)described herein as being performed by a WD. These operations, asperformed by processing circuitry 4120, may include processinginformation obtained by processing circuitry 4120 by, for example,converting the obtained information into other information, comparingthe obtained information or converted information to information storedby WD 4110, and/or performing one or more operations based on theobtained information or converted information, and as a result of saidprocessing making a determination.

Device readable medium 4130 may be operable to store a computer program,software, an application including one or more of logic, rules, code,tables, etc. and/or other instructions capable of being executed byprocessing circuitry 4120. Device readable medium 4130 may includecomputer memory (e.g., Random Access Memory (RAM) or Read Only Memory(ROM)), mass storage media (e.g., a hard disk), removable storage media(e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or anyother volatile or non-volatile, non-transitory device readable and/orcomputer executable memory devices that store information, data, and/orinstructions that may be used by processing circuitry 4120. In someembodiments, processing circuitry 4120 and device readable medium 4130may be considered to be integrated.

User interface equipment 4132 may provide components that allow for ahuman user to interact with WD 4110. Such interaction may be of manyforms, such as visual, audial, tactile, etc. User interface equipment4132 may be operable to produce output to the user and to allow the userto provide input to WD 4110. The type of interaction may vary dependingon the type of user interface equipment 4132 installed in WD 4110. Forexample, if WD 4110 is a smart phone, the interaction may be via a touchscreen; if WD 4110 is a smart meter, the interaction may be through ascreen that provides usage (e.g., the number of gallons used) or aspeaker that provides an audible alert (e.g., if smoke is detected).User interface equipment 4132 may include input interfaces, devices andcircuits, and output interfaces, devices and circuits. User interfaceequipment 4132 is configured to allow input of information into WD 4110,and is connected to processing circuitry 4120 to allow processingcircuitry 4120 to process the input information. User interfaceequipment 4132 may include, for example, a microphone, a proximity orother sensor, keys/buttons, a touch display, one or more cameras, a USBport, or other input circuitry. User interface equipment 4132 is alsoconfigured to allow output of information from WD 4110, and to allowprocessing circuitry 4120 to output information from WD 4110. Userinterface equipment 4132 may include, for example, a speaker, a display,vibrating circuitry, a USB port, a headphone interface, or other outputcircuitry. Using one or more input and output interfaces, devices, andcircuits, of user interface equipment 4132, WD 4110 may communicate withend users and/or the wireless network, and allow them to benefit fromthe functionality described herein.

Auxiliary equipment 4134 is operable to provide more specificfunctionality which may not be generally performed by WDs. This maycomprise specialized sensors for doing measurements for variouspurposes, interfaces for additional types of communication such as wiredcommunications etc. The inclusion and type of components of auxiliaryequipment 4134 may vary depending on the embodiment and/or scenario.

Power source 4136 may, in some embodiments, be in the form of a batteryor battery pack. Other types of power sources, such as an external powersource (e.g., an electricity outlet), photovoltaic devices or powercells, may also be used. WD 4110 may further comprise power circuitry4137 for delivering power from power source 4136 to the various parts ofWD 4110 which need power from power source 4136 to carry out anyfunctionality described or indicated herein. Power circuitry 4137 may incertain embodiments comprise power management circuitry. Power circuitry4137 may additionally or alternatively be operable to receive power froman external power source; in which case WD 4110 may be connectable tothe external power source (such as an electricity outlet) via inputcircuitry or an interface such as an electrical power cable. Powercircuitry 4137 may also in certain embodiments be operable to deliverpower from an external power source to power source 4136. This may be,for example, for the charging of power source 4136. Power circuitry 4137may perform any formatting, converting, or other modification to thepower from power source 4136 to make the power suitable for therespective components of WD 4110 to which power is supplied.

FIG. 22 illustrates a user Equipment in accordance with someembodiments.

FIG. 22 illustrates one embodiment of a UE in accordance with variousaspects described herein. As used herein, a user equipment or UE may notnecessarily have a user in the sense of a human user who owns and/oroperates the relevant device. Instead, a UE may represent a device thatis intended for sale to, or operation by, a human user but which maynot, or which may not initially, be associated with a specific humanuser (e.g., a smart sprinkler controller). Alternatively, a UE mayrepresent a device that is not intended for sale to, or operation by, anend user but which may be associated with or operated for the benefit ofa user (e.g., a smart power meter). UE 4200 may be any UE identified bythe 3rd Generation Partnership Project (3GPP), including a NB-IoT UE, amachine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.UE 4200, as illustrated in FIG. 22 , is one example of a WD configuredfor communication in accordance with one or more communication standardspromulgated by the 3rd Generation Partnership Project (3GPP), such as3GPP's GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, theterm WD and UE may be used interchangeable. Accordingly, although FIG.22 is a UE, the components discussed herein are equally applicable to aWD, and vice-versa.

In FIG. 22 , UE 4200 includes processing circuitry 4201 that isoperatively coupled to input/output interface 4205, radio frequency (RF)interface 4209, network connection interface 4211, memory 4215 includingrandom access memory (RAM) 4217, read-only memory (ROM) 4219, andstorage medium 4221 or the like, communication subsystem 4231, powersource 4233, and/or any other component, or any combination thereof.Storage medium 4221 includes operating system 4223, application program4225, and data 4227. In other embodiments, storage medium 4221 mayinclude other similar types of information. Certain UEs may utilize allof the components shown in FIG. 22 , or only a subset of the components.The level of integration between the components may vary from one UE toanother UE. Further, certain UEs may contain multiple instances of acomponent, such as multiple processors, memories, transceivers,transmitters, receivers, etc.

In FIG. 22 , processing circuitry 4201 may be configured to processcomputer instructions and data. Processing circuitry 4201 may beconfigured to implement any sequential state machine operative toexecute machine instructions stored as machine-readable computerprograms in the memory, such as one or more hardware-implemented statemachines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logictogether with appropriate firmware; one or more stored program,general-purpose processors, such as a microprocessor or Digital SignalProcessor (DSP), together with appropriate software; or any combinationof the above. For example, the processing circuitry 4201 may include twocentral processing units (CPUs). Data may be information in a formsuitable for use by a computer.

In the depicted embodiment, input/output interface 4205 may beconfigured to provide a communication interface to an input device,output device, or input and output device. UE 4200 may be configured touse an output device via input/output interface 4205. An output devicemay use the same type of interface port as an input device. For example,a USB port may be used to provide input to and output from UE 4200. Theoutput device may be a speaker, a sound card, a video card, a display, amonitor, a printer, an actuator, an emitter, a smartcard, another outputdevice, or any combination thereof. UE 4200 may be configured to use aninput device via input/output interface 4205 to allow a user to captureinformation into UE 4200. The input device may include a touch-sensitiveor presence-sensitive display, a camera (e.g., a digital camera, adigital video camera, a web camera, etc.), a microphone, a sensor, amouse, a trackball, a directional pad, a trackpad, a scroll wheel, asmartcard, and the like. The presence-sensitive display may include acapacitive or resistive touch sensor to sense input from a user. Asensor may be, for instance, an accelerometer, a gyroscope, a tiltsensor, a force sensor, a magnetometer, an optical sensor, a proximitysensor, another like sensor, or any combination thereof. For example,the input device may be an accelerometer, a magnetometer, a digitalcamera, a microphone, and an optical sensor.

In FIG. 22 , RF interface 4209 may be configured to provide acommunication interface to RF components such as a transmitter, areceiver, and an antenna. Network connection interface 4211 may beconfigured to provide a communication interface to network 4243 a.Network 4243 a may encompass wired and/or wireless networks such as alocal-area network (LAN), a wide-area network (WAN), a computer network,a wireless network, a telecommunications network, another like networkor any combination thereof. For example, network 4243 a may comprise aWi-Fi network. Network connection interface 4211 may be configured toinclude a receiver and a transmitter interface used to communicate withone or more other devices over a communication network according to oneor more communication protocols, such as Ethernet, TCP/IP, SONET, ATM,or the like. Network connection interface 4211 may implement receiverand transmitter functionality appropriate to the communication networklinks (e.g., optical, electrical, and the like). The transmitter andreceiver functions may share circuit components, software or firmware,or alternatively may be implemented separately.

RAM 4217 may be configured to interface via bus 4202 to processingcircuitry 4201 to provide storage or caching of data or computerinstructions during the execution of software programs such as theoperating system, application programs, and device drivers. ROM 4219 maybe configured to provide computer instructions or data to processingcircuitry 4201. For example, ROM 4219 may be configured to storeinvariant low-level system code or data for basic system functions suchas basic input and output (I/O), startup, or reception of keystrokesfrom a keyboard that are stored in a non-volatile memory. Storage medium4221 may be configured to include memory such as RAM, ROM, programmableread-only memory (PROM), erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), magneticdisks, optical disks, floppy disks, hard disks, removable cartridges, orflash drives. In one example, storage medium 4221 may be configured toinclude operating system 4223, application program 4225 such as a webbrowser application, a widget or gadget engine or another application,and data file 4227. Storage medium 4221 may store, for use by UE 4200,any of a variety of various operating systems or combinations ofoperating systems.

Storage medium 4221 may be configured to include a number of physicaldrive units, such as redundant array of independent disks (RAID), floppydisk drive, flash memory, USB flash drive, external hard disk drive,thumb drive, pen drive, key drive, high-density digital versatile disc(HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray opticaldisc drive, holographic digital data storage (HDDS) optical disc drive,external mini-dual in-line memory module (DIMM), synchronous dynamicrandom access memory (SDRAM), external micro-DIMM SDRAM, smartcardmemory such as a subscriber identity module or a removable user identity(SIM/RUIM) module, other memory, or any combination thereof. Storagemedium 4221 may allow UE 4200 to access computer-executableinstructions, application programs or the like, stored on transitory ornon-transitory memory media, to off-load data, or to upload data. Anarticle of manufacture, such as one utilizing a communication system maybe tangibly embodied in storage medium 4221, which may comprise a devicereadable medium.

In FIG. 22 , processing circuitry 4201 may be configured to communicatewith network 4243 b using communication subsystem 4231. Network 4243 aand network 4243 b may be the same network or networks or differentnetwork or networks. Communication subsystem 4231 may be configured toinclude one or more transceivers used to communicate with network 4243b. For example, communication subsystem 4231 may be configured toinclude one or more transceivers used to communicate with one or moreremote transceivers of another device capable of wireless communicationsuch as another WD, UE, or base station of a radio access network (RAN)according to one or more communication protocols, such as IEEE 802.11,CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver mayinclude transmitter 4233 and/or receiver 4235 to implement transmitteror receiver functionality, respectively, appropriate to the RAN links(e.g., frequency allocations and the like). Further, transmitter 4233and receiver 4235 of each transceiver may share circuit components,software or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions ofcommunication subsystem 4231 may include data communication, voicecommunication, multimedia communication, short-range communications suchas Bluetooth, near-field communication, location-based communicationsuch as the use of the global positioning system (GPS) to determine alocation, another like communication function, or any combinationthereof. For example, communication subsystem 4231 may include cellularcommunication, Wi-Fi communication, Bluetooth communication, and GPScommunication. Network 4243 b may encompass wired and/or wirelessnetworks such as a local-area network (LAN), a wide-area network (WAN),a computer network, a wireless network, a telecommunications network,another like network or any combination thereof. For example, network4243 b may be a cellular network, a Wi-Fi network, and/or a near-fieldnetwork. Power source 4213 may be configured to provide alternatingcurrent (AC) or direct current (DC) power to components of UE 4200.

The features, benefits and/or functions described herein may beimplemented in one of the components of UE 4200 or partitioned acrossmultiple components of UE 4200. Further, the features, benefits, and/orfunctions described herein may be implemented in any combination ofhardware, software or firmware. In one example, communication subsystem4231 may be configured to include any of the components describedherein. Further, processing circuitry 4201 may be configured tocommunicate with any of such components over bus 4202. In anotherexample, any of such components may be represented by programinstructions stored in memory that when executed by processing circuitry4201 perform the corresponding functions described herein. In anotherexample, the functionality of any of such components may be partitionedbetween processing circuitry 4201 and communication subsystem 4231. Inanother example, the non-computationally intensive functions of any ofsuch components may be implemented in software or firmware and thecomputationally intensive functions may be implemented in hardware.

FIG. 23 illustrates a virtualization environment in accordance with someembodiments.

FIG. 23 is a schematic block diagram illustrating a virtualizationenvironment 4300 in which functions implemented by some embodiments maybe virtualized. In the present context, virtualizing means creatingvirtual versions of apparatuses or devices which may includevirtualizing hardware platforms, storage devices and networkingresources. As used herein, virtualization can be applied to a node(e.g., a virtualized base station or a virtualized radio access node) orto a device (e.g., a UE, a wireless device or any other type ofcommunication device) or components thereof and relates to animplementation in which at least a portion of the functionality isimplemented as one or more virtual components (e.g., via one or moreapplications, components, functions, virtual machines or containersexecuting on one or more physical processing nodes in one or morenetworks).

In some embodiments, some or all of the functions described herein maybe implemented as virtual components executed by one or more virtualmachines implemented in one or more virtual environments 4300 hosted byone or more of hardware nodes 4330. Further, in embodiments in which thevirtual node is not a radio access node or does not require radioconnectivity (e.g., a core network node), then the network node may beentirely virtualized.

The functions may be implemented by one or more applications 4320 (whichmay alternatively be called software instances, virtual appliances,network functions, virtual nodes, virtual network functions, etc.)operative to implement some of the features, functions, and/or benefitsof some of the embodiments disclosed herein. Applications 4320 are runin virtualization environment 4300 which provides hardware 4330comprising processing circuitry 4360 and memory 4390. Memory 4390contains instructions 4395 executable by processing circuitry 4360whereby application 4320 is operative to provide one or more of thefeatures, benefits, and/or functions disclosed herein.

Virtualization environment 4300, comprises general-purpose orspecial-purpose network hardware devices 4330 comprising a set of one ormore processors or processing circuitry 4360, which may be commercialoff-the-shelf (COTS) processors, dedicated Application SpecificIntegrated Circuits (ASICs), or any other type of processing circuitryincluding digital or analog hardware components or special purposeprocessors. Each hardware device may comprise memory 4390-1 which may benon-persistent memory for temporarily storing instructions 4395 orsoftware executed by processing circuitry 4360. Each hardware device maycomprise one or more network interface controllers (NICs) 4370, alsoknown as network interface cards, which include physical networkinterface 4380. Each hardware device may also include non-transitory,persistent, machine-readable storage media 4390-2 having stored thereinsoftware 4395 and/or instructions executable by processing circuitry4360. Software 4395 may include any type of software including softwarefor instantiating one or more virtualization layers 4350 (also referredto as hypervisors), software to execute virtual machines 4340 as well assoftware allowing it to execute functions, features and/or benefitsdescribed in relation with some embodiments described herein.

Virtual machines 4340 comprise virtual processing, virtual memory,virtual networking or interface and virtual storage, and may be run by acorresponding virtualization layer 4350 or hypervisor. Differentembodiments of the instance of virtual appliance 4320 may be implementedon one or more of virtual machines 4340, and the implementations may bemade in different ways.

During operation, processing circuitry 4360 executes software 4395 toinstantiate the hypervisor or virtualization layer 4350, which maysometimes be referred to as a virtual machine monitor (VMM).Virtualization layer 4350 may present a virtual operating platform thatappears like networking hardware to virtual machine 4340.

As shown in FIG. 23 , hardware 4330 may be a standalone network nodewith generic or specific components. Hardware 4330 may comprise antenna43225 and may implement some functions via virtualization.Alternatively, hardware 4330 may be part of a larger cluster of hardware(e.g. such as in a data center or customer premise equipment (CPE))where many hardware nodes work together and are managed via managementand orchestration (MANO) 43100, which, among others, oversees lifecyclemanagement of applications 4320.

Virtualization of the hardware is in some contexts referred to asnetwork function virtualization (NFV). NFV may be used to consolidatemany network equipment types onto industry standard high volume serverhardware, physical switches, and physical storage, which can be locatedin data centers, and customer premise equipment.

In the context of NFV, virtual machine 4340 may be a softwareimplementation of a physical machine that runs programs as if they wereexecuting on a physical, non-virtualized machine. Each of virtualmachines 4340, and that part of hardware 4330 that executes that virtualmachine, be it hardware dedicated to that virtual machine and/orhardware shared by that virtual machine with others of the virtualmachines 4340, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) isresponsible for handling specific network functions that run in one ormore virtual machines 4340 on top of hardware networking infrastructure4330 and corresponds to application 4320 in FIG. 23 .

In some embodiments, one or more radio units 43200 that each include oneor more transmitters 43220 and one or more receivers 43210 may becoupled to one or more antennas 43225. Radio units 43200 may communicatedirectly with hardware nodes 4330 via one or more appropriate networkinterfaces and may be used in combination with the virtual components toprovide a virtual node with radio capabilities, such as a radio accessnode or a base station.

In some embodiments, some signalling can be effected with the use ofcontrol system 43230 which may alternatively be used for communicationbetween the hardware nodes 4330 and radio units 43200.

FIG. 24 illustrates a telecommunication network connected via anintermediate network to a host computer in accordance with someembodiments.

With reference to FIG. 24 , in accordance with an embodiment, acommunication system includes telecommunication network 4410, such as a3GPP-type cellular network, which comprises access network 4411, such asa radio access network, and core network 4414. Access network 4411comprises a plurality of base stations 4412 a, 4412 b, 4412 c, such asNBs, eNBs, gNBs or other types of wireless access points, each defininga corresponding coverage area 4413 a, 4413 b, 4413 c. Each base station4412 a, 4412 b, 4412 c is connectable to core network 4414 over a wiredor wireless connection 4415. A first UE 4491 located in coverage area4413 c is configured to wirelessly connect to, or be paged by, thecorresponding base station 4412 c. A second UE 4492 in coverage area4413 a is wirelessly connectable to the corresponding base station 4412a. While a plurality of UEs 4491, 4492 are illustrated in this example,the disclosed embodiments are equally applicable to a situation where asole UE is in the coverage area or where a sole UE is connecting to thecorresponding base station 4412.

Telecommunication network 4410 is itself connected to host computer4430, which may be embodied in the hardware and/or software of astandalone server, a cloud-implemented server, a distributed server oras processing resources in a server farm. Host computer 4430 may beunder the ownership or control of a service provider, or may be operatedby the service provider or on behalf of the service provider.Connections 4421 and 4422 between telecommunication network 4410 andhost computer 4430 may extend directly from core network 4414 to hostcomputer 4430 or may go via an optional intermediate network 4420.Intermediate network 4420 may be one of, or a combination of more thanone of, a public, private or hosted network; intermediate network 4420,if any, may be a backbone network or the Internet; in particular,intermediate network 4420 may comprise two or more sub-networks (notshown).

The communication system of FIG. 24 as a whole enables connectivitybetween the connected UEs 4491, 4492 and host computer 4430. Theconnectivity may be described as an over-the-top (OTT) connection 4450.Host computer 4430 and the connected UEs 4491, 4492 are configured tocommunicate data and/or signaling via OTT connection 4450, using accessnetwork 4411, core network 4414, any intermediate network 4420 andpossible further infrastructure (not shown) as intermediaries. OTTconnection 4450 may be transparent in the sense that the participatingcommunication devices through which OTT connection 4450 passes areunaware of routing of uplink and downlink communications. For example,base station 4412 may not or need not be informed about the past routingof an incoming downlink communication with data originating from hostcomputer 4430 to be forwarded (e.g., handed over) to a connected UE4491. Similarly, base station 4412 need not be aware of the futurerouting of an outgoing uplink communication originating from the UE 4491towards the host computer 4430.

FIG. 25 illustrates a host computer communicating via a base stationwith a user equipment over a partially wireless connection in accordancewith some embodiments.

Example implementations, in accordance with an embodiment, of the UE,base station and host computer discussed in the preceding paragraphswill now be described with reference to FIG. 25 . In communicationsystem 4500, host computer 4510 comprises hardware 4515 includingcommunication interface 4516 configured to set up and maintain a wiredor wireless connection with an interface of a different communicationdevice of communication system 4500. Host computer 4510 furthercomprises processing circuitry 4518, which may have storage and/orprocessing capabilities. In particular, processing circuitry 4518 maycomprise one or more programmable processors, application-specificintegrated circuits, field programmable gate arrays or combinations ofthese (not shown) adapted to execute instructions. Host computer 4510further comprises software 4511, which is stored in or accessible byhost computer 4510 and executable by processing circuitry 4518. Software4511 includes host application 4512. Host application 4512 may beoperable to provide a service to a remote user, such as UE 4530connecting via OTT connection 4550 terminating at UE 4530 and hostcomputer 4510. In providing the service to the remote user, hostapplication 4512 may provide user data which is transmitted using OTTconnection 4550.

Communication system 4500 further includes base station 4520 provided ina telecommunication system and comprising hardware 4525 enabling it tocommunicate with host computer 4510 and with UE 4530. Hardware 4525 mayinclude communication interface 4526 for setting up and maintaining awired or wireless connection with an interface of a differentcommunication device of communication system 4500, as well as radiointerface 4527 for setting up and maintaining at least wirelessconnection 4570 with UE 4530 located in a coverage area (not shown inFIG. 25 ) served by base station 4520. Communication interface 4526 maybe configured to facilitate connection 4560 to host computer 4510.Connection 4560 may be direct or it may pass through a core network (notshown in FIG. 25 ) of the telecommunication system and/or through one ormore intermediate networks outside the telecommunication system. In theembodiment shown, hardware 4525 of base station 4520 further includesprocessing circuitry 4528, which may comprise one or more programmableprocessors, application-specific integrated circuits, field programmablegate arrays or combinations of these (not shown) adapted to executeinstructions. Base station 4520 further has software 4521 storedinternally or accessible via an external connection.

Communication system 4500 further includes UE 4530 already referred to.Its hardware 4535 may include radio interface 4537 configured to set upand maintain wireless connection 4570 with a base station serving acoverage area in which UE 4530 is currently located. Hardware 4535 of UE4530 further includes processing circuitry 4538, which may comprise oneor more programmable processors, application-specific integratedcircuits, field programmable gate arrays or combinations of these (notshown) adapted to execute instructions. UE 4530 further comprisessoftware 4531, which is stored in or accessible by UE 4530 andexecutable by processing circuitry 4538. Software 4531 includes clientapplication 4532. Client application 4532 may be operable to provide aservice to a human or non-human user via UE 4530, with the support ofhost computer 4510. In host computer 4510, an executing host application4512 may communicate with the executing client application 4532 via OTTconnection 4550 terminating at UE 4530 and host computer 4510. Inproviding the service to the user, client application 4532 may receiverequest data from host application 4512 and provide user data inresponse to the request data. OTT connection 4550 may transfer both therequest data and the user data. Client application 4532 may interactwith the user to generate the user data that it provides.

It is noted that host computer 4510, base station 4520 and UE 4530illustrated in FIG. 25 may be similar or identical to host computer4430, one of base stations 4412 a, 4412 b, 4412 c and one of UEs 4491,4492 of FIG. 24 , respectively. This is to say, the inner workings ofthese entities may be as shown in FIG. 25 and independently, thesurrounding network topology may be that of FIG. 24 .

In FIG. 25 , OTT connection 4550 has been drawn abstractly to illustratethe communication between host computer 4510 and UE 4530 via basestation 4520, without explicit reference to any intermediary devices andthe precise routing of messages via these devices. Networkinfrastructure may determine the routing, which it may be configured tohide from UE 4530 or from the service provider operating host computer4510, or both. While OTT connection 4550 is active, the networkinfrastructure may further take decisions by which it dynamicallychanges the routing (e.g., on the basis of load balancing considerationor reconfiguration of the network).

Wireless connection 4570 between UE 4530 and base station 4520 is inaccordance with the teachings of the embodiments described throughoutthis disclosure. One or more of the various embodiments may improve theperformance of OTT services provided to UE 4530 using OTT connection4550, in which wireless connection 4570 forms the last segment. Moreprecisely, the teachings of these embodiments may improve the randomaccess speed and/or reduce random access failure rates and therebyprovide benefits such as faster and/or more reliable random access.

A measurement procedure may be provided for the purpose of monitoringdata rate, latency and other factors on which the one or moreembodiments improve. There may further be an optional networkfunctionality for reconfiguring OTT connection 4550 between hostcomputer 4510 and UE 4530, in response to variations in the measurementresults. The measurement procedure and/or the network functionality forreconfiguring OTT connection 4550 may be implemented in software 4511and hardware 4515 of host computer 4510 or in software 4531 and hardware4535 of UE 4530, or both. In embodiments, sensors (not shown) may bedeployed in or in association with communication devices through whichOTT connection 4550 passes; the sensors may participate in themeasurement procedure by supplying values of the monitored quantitiesexemplified above, or supplying values of other physical quantities fromwhich software 4511, 4531 may compute or estimate the monitoredquantities. The reconfiguring of OTT connection 4550 may include messageformat, retransmission settings, preferred routing etc.; thereconfiguring need not affect base station 4520, and it may be unknownor imperceptible to base station 4520. Such procedures andfunctionalities may be known and practiced in the art. In certainembodiments, measurements may involve proprietary UE signalingfacilitating host computer 4510's measurements of throughput,propagation times, latency and the like. The measurements may beimplemented in that software 4511 and 4531 causes messages to betransmitted, in particular empty or ‘dummy’ messages, using OTTconnection 4550 while it monitors propagation times, errors etc.

FIG. 26 illustrates methods implemented in a communication systemincluding a host computer, a base station and a user equipment inaccordance with some embodiments

FIG. 26 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 24 and 25 . Forsimplicity of the present disclosure, only drawing references to FIG. 26will be included in this section. In step 4610, the host computerprovides user data. In substep 4611 (which may be optional) of step4610, the host computer provides the user data by executing a hostapplication. In step 4620, the host computer initiates a transmissioncarrying the user data to the UE. In step 4630 (which may be optional),the base station transmits to the UE the user data which was carried inthe transmission that the host computer initiated, in accordance withthe teachings of the embodiments described throughout this disclosure.In step 4640 (which may also be optional), the UE executes a clientapplication associated with the host application executed by the hostcomputer.

FIG. 27 illustrates methods implemented in a communication systemincluding a host computer, a base station and a user equipment inaccordance with some embodiments.

FIG. 27 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 24 and 25 . Forsimplicity of the present disclosure, only drawing references to FIG. 27will be included in this section. In step 4710 of the method, the hostcomputer provides user data. In an optional substep (not shown) the hostcomputer provides the user data by executing a host application. In step4720, the host computer initiates a transmission carrying the user datato the UE. The transmission may pass via the base station, in accordancewith the teachings of the embodiments described throughout thisdisclosure. In step 4730 (which may be optional), the UE receives theuser data carried in the transmission.

FIG. 28 illustrates methods implemented in a communication systemincluding a host computer, a base station and a user equipment inaccordance with some embodiments

FIG. 28 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 24 and 25 . Forsimplicity of the present disclosure, only drawing references to FIG. 28will be included in this section. In step 4810 (which may be optional),the UE receives input data provided by the host computer. Additionallyor alternatively, in step 4820, the UE provides user data. In substep4821 (which may be optional) of step 4820, the UE provides the user databy executing a client application. In substep 4811 (which may beoptional) of step 4810, the UE executes a client application whichprovides the user data in reaction to the received input data providedby the host computer. In providing the user data, the executed clientapplication may further consider user input received from the user.Regardless of the specific manner in which the user data was provided,the UE initiates, in substep 4830 (which may be optional), transmissionof the user data to the host computer. In step 4840 of the method, thehost computer receives the user data transmitted from the UE, inaccordance with the teachings of the embodiments described throughoutthis disclosure.

FIG. 29 illustrates methods implemented in a communication systemincluding a host computer, a base station and a user equipment inaccordance with some embodiments

FIG. 29 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 24 and 25 . Forsimplicity of the present disclosure, only drawing references to FIG. 29will be included in this section. In step 4910 (which may be optional),in accordance with the teachings of the embodiments described throughoutthis disclosure, the base station receives user data from the UE. Instep 4920 (which may be optional), the base station initiatestransmission of the received user data to the host computer. In step4930 (which may be optional), the host computer receives the user datacarried in the transmission initiated by the base station.

Any appropriate steps, methods, features, functions, or benefitsdisclosed herein may be performed through one or more functional unitsor modules of one or more virtual apparatuses. Each virtual apparatusmay comprise a number of these functional units. These functional unitsmay be implemented via processing circuitry, which may include one ormore microprocessor or microcontrollers, as well as other digitalhardware, which may include digital signal processors (DSPs),special-purpose digital logic, and the like. The processing circuitrymay be configured to execute program code stored in memory, which mayinclude one or several types of memory such as read-only memory (ROM),random-access memory (RAM), cache memory, flash memory devices, opticalstorage devices, etc. Program code stored in memory includes programinstructions for executing one or more telecommunications and/or datacommunications protocols as well as instructions for carrying out one ormore of the techniques described herein. In some implementations, theprocessing circuitry may be used to cause the respective functional unitto perform corresponding functions according one or more embodiments ofthe present disclosure.

The term unit may have conventional meaning in the field of electronics,electrical devices and/or electronic devices and may include, forexample, electrical and/or electronic circuitry, devices, modules,processors, memories, logic solid state and/or discrete devices,computer programs or instructions for carrying out respective tasks,procedures, computations, outputs, and/or displaying functions, and soon, as such as those that are described herein.

ABBREVIATIONS

At least some of the following abbreviations may be used in thisdisclosure. If there is an inconsistency between abbreviations,preference should be given to how it is used above. If listed multipletimes below, the first listing should be preferred over any subsequentlisting(s).

-   -   1×RTT CDMA2000 1× Radio Transmission Technology    -   3GPP 3rd Generation Partnership Project    -   5G 5th Generation    -   ABS Almost Blank Subframe    -   ARQ Automatic Repeat Request    -   AWGN Additive White Gaussian Noise    -   BCCH Broadcast Control Channel    -   BCH Broadcast Channel    -   CA Carrier Aggregation    -   CC Carrier Component    -   CCCH SDU Common Control Channel SDU    -   CDMA Code Division Multiplexing Access    -   CGI Cell Global Identifier    -   CIR Channel Impulse Response    -   CP Cyclic Prefix    -   CPICH Common Pilot Channel    -   CPICH Ec/No CPICH Received energy per chip divided by the power        density in the band    -   CQI Channel Quality information    -   C-RNTI Cell RNTI    -   CSI Channel State Information    -   DCCH Dedicated Control Channel    -   DL Downlink    -   DM Demodulation    -   DMRS Demodulation Reference Signal    -   DRX Discontinuous Reception    -   DTX Discontinuous Transmission    -   DTCH Dedicated Traffic Channel    -   DUT Device Under Test    -   E-CID Enhanced Cell-ID (positioning method)    -   E-SMLC Evolved-Serving Mobile Location Centre    -   ECGI Evolved CGI    -   eNB E-UTRAN NodeB    -   ePDCCH enhanced Physical Downlink Control Channel    -   E-SMLC evolved Serving Mobile Location Center    -   E-UTRA Evolved UTRA    -   E-UTRAN Evolved UTRAN    -   FDD Frequency Division Duplex    -   FFS For Further Study    -   GERAN GSM EDGE Radio Access Network    -   gNB Base station in NR    -   GNSS Global Navigation Satellite System    -   GSM Global System for Mobile communication    -   HARQ Hybrid Automatic Repeat Request    -   HO Handover    -   HSPA High Speed Packet Access    -   HRPD High Rate Packet Data    -   LOS Line of Sight    -   LPP LTE Positioning Protocol    -   LTE Long-Term Evolution    -   MAC Medium Access Control    -   MBMS Multimedia Broadcast Multicast Services    -   MBSFN Multimedia Broadcast multicast service Single Frequency        Network    -   MBSFN ABS MBSFN Almost Blank Subframe    -   MDT Minimization of Drive Tests    -   MIB Master Information Block    -   MME Mobility Management Entity    -   MSC Mobile Switching Center    -   NPDCCH Narrowband Physical Downlink Control Channel    -   NR New Radio    -   OCNG OFDMA Channel Noise Generator    -   OFDM Orthogonal Frequency Division Multiplexing    -   OFDMA Orthogonal Frequency Division Multiple Access    -   OSS Operations Support System    -   OTDOA Observed Time Difference of Arrival    -   O&M Operation and Maintenance    -   PBCH Physical Broadcast Channel    -   P-CCPCH Primary Common Control Physical Channel    -   PCell Primary Cell    -   PCFICH Physical Control Format Indicator Channel    -   PDCCH Physical Downlink Control Channel    -   PDP Profile Delay Profile    -   PDSCH Physical Downlink Shared Channel    -   PGW Packet Gateway    -   PHICH Physical Hybrid-ARQ Indicator Channel    -   PLMN Public Land Mobile Network    -   PMI Precoder Matrix Indicator    -   PRACH Physical Random Access Channel    -   PRS Positioning Reference Signal    -   PSS Primary Synchronization Signal    -   PUCCH Physical Uplink Control Channel    -   PUSCH Physical Uplink Shared Channel    -   RACH Random Access Channel    -   QAM Quadrature Amplitude Modulation    -   RAN Radio Access Network    -   RAT Radio Access Technology    -   RLM Radio Link Management    -   RNC Radio Network Controller    -   RNTI Radio Network Temporary Identifier    -   RRC Radio Resource Control    -   RRM Radio Resource Management    -   RS Reference Signal    -   RSCP Received Signal Code Power    -   RSRP Reference Symbol Received Power OR Reference Signal        Received Power    -   RSRQ Reference Signal Received Quality OR Reference Symbol        Received Quality    -   RSSI Received Signal Strength Indicator    -   RSTD Reference Signal Time Difference    -   SCH Synchronization Channel    -   SCell Secondary Cell    -   SDU Service Data Unit    -   SFN System Frame Number    -   SGW Serving Gateway    -   SI System Information    -   SIB System Information Block    -   SNR Signal to Noise Ratio    -   SON Self Optimized Network    -   SS Synchronization Signal    -   SSS Secondary Synchronization Signal    -   TDD Time Division Duplex    -   TDOA Time Difference of Arrival    -   TOA Time of Arrival    -   TSS Tertiary Synchronization Signal    -   TTI Transmission Time Interval    -   UE User Equipment    -   UL Uplink    -   UMTS Universal Mobile Telecommunication System    -   USIM Universal Subscriber Identity Module    -   UTDOA Uplink Time Difference of Arrival    -   UTRA Universal Terrestrial Radio Access    -   UTRAN Universal Terrestrial Radio Access Network    -   WCDMA Wide CDMA    -   WLAN Wide Local Area Network

Further definitions and embodiments are discussed below.

In the above-description of various embodiments of present inventiveconcepts, it is to be understood that the terminology used herein is forthe purpose of describing particular embodiments only and is notintended to be limiting of present inventive concepts. Unless otherwisedefined, all terms (including technical and scientific terms) usedherein have the same meaning as commonly understood by one of ordinaryskill in the art to which present inventive concepts belong. It will befurther understood that terms, such as those defined in commonly useddictionaries, should be interpreted as having a meaning that isconsistent with their meaning in the context of this specification andthe relevant art and will not be interpreted in an idealized or overlyformal sense unless expressly so defined herein.

When an element is referred to as being “connected”, “coupled”,“responsive”, or variants thereof to another element, it can be directlyconnected, coupled, or responsive to the other element or interveningelements may be present. In contrast, when an element is referred to asbeing “directly connected”, “directly coupled”, “directly responsive”,or variants thereof to another element, there are no interveningelements present. Like numbers refer to like elements throughout.Furthermore, “coupled”, “connected”, “responsive”, or variants thereofas used herein may include wirelessly coupled, connected, or responsive.As used herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. Well-known functions or constructions may not be described indetail for brevity and/or clarity. The term “and/or” (abbreviated “/”)includes any and all combinations of one or more of the associatedlisted items.

It will be understood that although the terms first, second, third, etc.may be used herein to describe various elements/operations, theseelements/operations should not be limited by these terms. These termsare only used to distinguish one element/operation from anotherelement/operation. Thus a first element/operation in some embodimentscould be termed a second element/operation in other embodiments withoutdeparting from the teachings of present inventive concepts. The samereference numerals or the same reference designators denote the same orsimilar elements throughout the specification.

As used herein, the terms “comprise”, “comprising”, “comprises”,“include”, “including”, “includes”, “have”, “has”, “having”, or variantsthereof are open-ended, and include one or more stated features,integers, elements, steps, components or functions but does not precludethe presence or addition of one or more other features, integers,elements, steps, components, functions or groups thereof. Furthermore,as used herein, the common abbreviation “e.g.”, which derives from theLatin phrase “exempli gratia,” may be used to introduce or specify ageneral example or examples of a previously mentioned item, and is notintended to be limiting of such item. The common abbreviation “i.e.”,which derives from the Latin phrase “id est,” may be used to specify aparticular item from a more general recitation.

Example embodiments are described herein with reference to blockdiagrams and/or flowchart illustrations of computer-implemented methods,apparatus (systems and/or devices) and/or computer program products. Itis understood that a block of the block diagrams and/or flowchartillustrations, and combinations of blocks in the block diagrams and/orflowchart illustrations, can be implemented by computer programinstructions that are performed by one or more computer circuits. Thesecomputer program instructions may be provided to a processor circuit ofa general purpose computer circuit, special purpose computer circuit,and/or other programmable data processing circuit to produce a machine,such that the instructions, which execute via the processor of thecomputer and/or other programmable data processing apparatus, transformand control transistors, values stored in memory locations, and otherhardware components within such circuitry to implement thefunctions/acts specified in the block diagrams and/or flowchart block orblocks, and thereby create means (functionality) and/or structure forimplementing the functions/acts specified in the block diagrams and/orflowchart block(s).

These computer program instructions may also be stored in a tangiblecomputer-readable medium that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablemedium produce an article of manufacture including instructions whichimplement the functions/acts specified in the block diagrams and/orflowchart block or blocks. Accordingly, embodiments of present inventiveconcepts may be embodied in hardware and/or in software (includingfirmware, resident software, micro-code, etc.) that runs on a processorsuch as a digital signal processor, which may collectively be referredto as “circuitry,” “a module” or variants thereof.

It should also be noted that in some alternate implementations, thefunctions/acts noted in the blocks may occur out of the order noted inthe flowcharts. For example, two blocks shown in succession may in factbe executed substantially concurrently or the blocks may sometimes beexecuted in the reverse order, depending upon the functionality/actsinvolved. Moreover, the functionality of a given block of the flowchartsand/or block diagrams may be separated into multiple blocks and/or thefunctionality of two or more blocks of the flowcharts and/or blockdiagrams may be at least partially integrated. Finally, other blocks maybe added/inserted between the blocks that are illustrated, and/orblocks/operations may be omitted without departing from the scope ofinventive concepts. Moreover, although some of the diagrams includearrows on communication paths to show a primary direction ofcommunication, it is to be understood that communication may occur inthe opposite direction to the depicted arrows.

Many variations and modifications can be made to the embodiments withoutsubstantially departing from the principles of the present inventiveconcepts. All such variations and modifications are intended to beincluded herein within the scope of present inventive concepts.Accordingly, the above disclosed subject matter is to be consideredillustrative, and not restrictive, and the examples of embodiments areintended to cover all such modifications, enhancements, and otherembodiments, which fall within the spirit and scope of present inventiveconcepts. Thus, to the maximum extent allowed by law, the scope ofpresent inventive concepts are to be determined by the broadestpermissible interpretation of the present disclosure including theexamples of embodiments and their equivalents, and shall not berestricted or limited by the foregoing detailed description.

1. A method of operating a Radio Access Network, RAN, node of a wirelesscommunication network, the method comprising: obtaining informationdefining an operational environment in which a wireless device isoperating; and managing communication with the wireless device based onthe information defining the operational environment in which thewireless device is operating.
 2. The method of claim 1 furthercomprising: receiving a measurement of received signal quality and/orreceived signal power from the wireless device, wherein the measurementis a measurement of the received signal quality and/or the receivedsignal power at the wireless device, and wherein communication with thewireless device is managed based on the information defining theoperational environment in which the wireless device is operating andbased on the measurement of the received signal quality and/or thereceived signal power.
 3. The method of claim 2, wherein the receivedsignal quality and/or the received signal power is for at least one beamreceived by the wireless device from the RAN node.
 4. The method ofclaim 2, wherein the received signal quality and/or the received signalpower comprises a Reference Signal Received Quality, RSRQ, and/or aReference Signal Received Power, RSRP.
 5. The method of claim 1, whereinmanaging communication comprises performing beam management for thewireless device based on the information defining the operationalenvironment in which the wireless device is operating.
 6. The method ofclaim 5, where performing beam management comprises performing beamadjustment and/or beam alignment for the wireless device based on theinformation defining the operation environment in which the wirelessdevice is operating.
 7. The method of claim 5, wherein performing beammanagement comprises selecting a beam for communication with thewireless device based on the information defining the operationalenvironment in which the wireless device is operating, and communicatingdata with the wireless device using the beam selected for communicationwith the wireless device.
 8. The method of claim 1, wherein the RAN nodeis a first RAN node, wherein managing communication comprises performinghandover of the wireless device from the first RAN node to a second RANnode based on the information defining the operational environment inwhich the wireless device is operating.
 9. The method of claim 1,wherein managing communication comprises performing carrier aggregationfor the wireless device based on the information defining theoperational environment in which the wireless device is operating. 10.The method of claim 9, wherein performing carrier aggregation comprisesselecting at least one component carrier to provide carrier aggregationfor the wireless device, and communicating data with the wireless deviceusing the at least one component carrier selected to provide carrieraggregation.
 11. The method of claim 1, wherein managing communicationcomprises controlling transmission of a reference signal based on theinformation defining the operational environment in which the wirelessdevice is operating.
 12. The method of claim 11, wherein controllingtransmission comprises selecting a beam for the reference signal basedon the information defining the operational environment in which thewireless device is operating, and transmitting the reference signalusing the beam selected for the reference signal.
 13. The method ofclaim 11, wherein the reference signal comprises at least one of apositioning reference signal, PRS, a channel state information referencesignal, CSI-RS, and/or cell specific reference signal, CRS.
 14. Themethod of claim 1, wherein the information defining the operationalenvironment comprises an indication that the wireless device is in lineof sight, LOS, or non-line of sight, NLOS, communication with the RANnode.
 15. The method of claim 14, wherein obtaining the informationdefining the operational environment comprises receiving the indicationthat the wireless device in LOS or NLOS communication with the RAN nodefrom the wireless device.
 16. The method of claim 14, wherein obtainingthe information defining the operational environment comprises receivinga representation of a power delay profile, PDP, from the wirelessdevice, and determining the indication based on the representation ofthe PDP.
 17. The method of claim 1, wherein the information defining theoperational environment comprises an indication that the wireless deviceis indoors, semi-indoors, or outdoors.
 18. The method of claim 17,wherein obtaining the information defining the operational environmentcomprises receiving an identification of a location information sourcefrom the wireless device identifying a source used by the wirelessdevice to determine a location of the wireless device and determiningwhether the wireless device is indoors, semi-indoors, or outdoors basedon the identification of the location information source.
 19. The methodof claim 18, wherein the identification of the location informationsource identifies a global navigation satellite system, GNSS, source andwherein the wireless device is determined to be outdoors based onidentification of the GNSS source.
 20. The method of claim 18, whereinthe identification of the location information source identifies awireless local area network, WLAN, source and/or a Bluetooth, BT,source, and wherein the wireless device is determined to be indoorsbased on identification of the WLAN source and/or the BT source. 21-37.(canceled)